How to restrict shard auto failover in elasticsearch

Elastic Stack Elasticsearch
1

Looking for help with restricting shard auto failover. If we have 1000
indexes and some times it requires nodes to be restarted. In the event of
node restarts shards are automatically failed over or getting rebuilt on
different nodes. This is causing lot of time to build and recover. Instead,
is there a way disable shard failover and restart the node will bring it
back shards online immediately.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

2

If the node restart is planned, you can temporarily disable shard
allocation with:

cluster.routing.allocation.disable_allocation or
cluster.routing.allocation.disable_replica_allocation

Check out the cluster shard allocation pagehttp://www.elasticsearch.org/guide/reference/modules/cluster.htmlfor more details. Note that replicas will still be promoted to primaries if
a primary goes down, and ES will still sync various changes when the node
comes back up.

-Zach

On Tuesday, February 19, 2013 1:41:22 AM UTC-5, Krishna Reddy wrote:

Looking for help with restricting shard auto failover. If we have 1000
indexes and some times it requires nodes to be restarted. In the event of
node restarts shards are automatically failed over or getting rebuilt on
different nodes. This is causing lot of time to build and recover. Instead,
is there a way disable shard failover and restart the node will bring it
back shards online immediately.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

3

Thank Zach it was helpful and worked for us.

On Tuesday, February 19, 2013 3:49:45 AM UTC-8, Zachary Tong wrote:

If the node restart is planned, you can temporarily disable shard
allocation with:

cluster.routing.allocation.disable_allocation or
cluster.routing.allocation.disable_replica_allocation

Check out the cluster shard allocation pagehttp://www.elasticsearch.org/guide/reference/modules/cluster.htmlfor more details. Note that replicas will still be promoted to primaries if
a primary goes down, and ES will still sync various changes when the node
comes back up.

-Zach

On Tuesday, February 19, 2013 1:41:22 AM UTC-5, Krishna Reddy wrote:

Looking for help with restricting shard auto failover. If we have 1000
indexes and some times it requires nodes to be restarted. In the event of
node restarts shards are automatically failed over or getting rebuilt on
different nodes. This is causing lot of time to build and recover. Instead,
is there a way disable shard failover and restart the node will bring it
back shards online immediately.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.