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 putting nodes (which were hot) onto the warm node allocators. Performance was not bad (on AWS), but we realize that this is problematic and are looking at how to fix this now.
Yes, our Admin-Console-Elasticsearch is Now ALSO on WARM.. which is clearly not ideal.
A) Modify the Template to use a new instance configuration id (HOT node format).
... If we do.. how can we roll this out? It isn't taking effect immediatly, so appears we need to run the plan for it to take effect.
B) Should we create a NEW Plan, and then change the Cluster to use the New Plan.
.... I know we couldn't do a hot/warm migration in one version, but not sure about 2.2.2
... Will this change the ElasticSearch cluster id if we do this?
C) something else