Thanks Ivan for the suggestions, I'll try to make use of them. Drew, Sorry I din't get the part when you said "There's nothing wrong with having a yellow cluster" And yes I agree ES does a good job of rebalancing but just think of a case where you have close to few hundred GBs of data per shard which will move around the cluster even though the new node takes only few minutes to come back up. Hence, looking to avoid unnecessary network i/O.
-- Sagar On Friday, June 6, 2014 2:41:37 PM UTC-7, Drew Raines wrote: > > sagarl wrote: > > > We have our ES cluster running on aws instances where nodes can > > come and go. We would like to disable Shard reallocation on > > cluster in Normal state so that Node going down should not > > rebalance the shards.(Just to avoid unnecessary Network i/o). > > If your shard topology is relatively static, you could just leave > allocation disabled (or set it to new_primaries for the occasional > index creation). But honestly you're trying to micro-manage a > process that ES does pretty well. There's nothing wrong with > having a yellow cluster. If you're concerned about availability > you should add replicas. > > Drew > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/386d674e-52b8-4ed1-95ce-6efcf03718c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
