If you disable shard allocation, you disable the internal automatic load balancing, ES will not be able to help distributing search/index requests by itself. Personally I have much difficulties in disabling shard allocation (except for node decomissioinng) because I really like the magic behind the auto shard movements.
The shard moves are designed to run in the background. Unless your shards are gigantic, or your shard numbers are huge, this process will not influence the normal cluster operation. It will just take some time to complete, which might be bothering. In that case, maybe the total number of nodes does not suffice to handle shard movements and should be increased. This is a matter of sizing the whole cluster correctly. Replica level can be increased for two reasons. First, to distribute search load. Second, to allow more nodes to fail simultaneously. Jörg On Thu, Feb 13, 2014 at 11:33 PM, Mohit Anchlia <[email protected]>wrote: > This is interesting, I was thinking by having more replicas we can work > around issues when few nodes go down. Is this more challenging than that? I > am trying to understand where should I put more focus on to get HA search > solution. We have large data sets so I also worry about too much index > movement causing performance issues. Is there a downside of completely > disabling shard allocation. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGDbtF7GY14z%3DTPKaumTNJssb4Ce1hq_ENiuOibGRVhgg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
