What happens if I explicitly route a shard to a different node while the indexing happens to that shard in the original shard?
Should I stop indexing in that shard?
When you move a shard to a different node a replica is first created on the new node. Once this is in sync with the primary shard it can be promoted and the original primary shard removed. This is what happens behind the scenes when Elasticsearch moves shards due to events in the cluster, so there is no need to stop indexing.
Hi, thank you so much for the response. One more doubt, in case there is constant indexing happening to the shard I am trying to move to the new node, will the indexing delay the process of promoting the replica to primary in the new shard?
No. This will be handled seamlessly.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.