In moving to Hot-Warm nodes, our Prior Template did NOT have an instance configuration that used the box_type values. So, migrating a cluster to hot-warm configuration went fine, and it started proplerly using WARM node allocators. However, the clusters using the OLD Template eventually started p…

Hot-Warm migration - Need to update PRIOR Template (Hot-Only) to recognize WARM Allocators are not valid targets

system (system) Closed June 26, 2019, 8:50pm 4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
How do ECE Cloud UI Hot-Warm and Index Management Hot-Warm join up Elastic Cloud Enterprise (ECE)	9	1104	April 29, 2020
Questions on Hot-Warm Deployment Runners and Data Migration Elastic Cloud Enterprise (ECE)	4	612	July 19, 2019
Adding warm node to existing cluster, how to avoid existing indices to spread to these nodes Elasticsearch	6	1038	October 27, 2020
Shard allocation with hot - warm stacks Elasticsearch	1	357	August 20, 2019
Cluster-Default index allocation box? Elasticsearch	2	1377	February 24, 2017