Rebalancing of shards during temporary unavailability of one node


(AshutoshB) #1

Hi All,

I have a question regarding the re-balancing of shards on es nodes. Let’s
suppose that we have 3 es nodes with 5 indices (each index has 5 shards and
one replica). So the total 50 shards will be distributed over 3 nodes
initially. If for some reason (may be due to network issue or the es
process on the node is killed) one node goes out of the cluster then the
rest of the 2 nodes will start re-balancing the missing shards.

Is my understanding correct?

Is there any configuration to direct es not to start re-balancing
immediately but to wait for some configured time?

For example, the following configuration can be used to introduce delay or
wait time during the full cluster restart:

gateway.recovery_after_nodes

gateway.recovery_after_time

gateway.expected_nodes

I am looking for similar parameters to introduce similar type of delay time
during temporary unavailability of one node in the whole cluster.

Thank you in advance.

Best,

Ashutosh

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b4835941-4226-4d56-8101-3b468d381be7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #2