The cluster.routing.allocation.exclude._ip config - see http://blog.sematext.com/2012/05/29/elasticsearch-shard-placement-control/
-- Itamar Syn-Hershko http://code972.com | @synhershko <https://twitter.com/synhershko> Freelance Developer & Consultant Author of RavenDB in Action <http://manning.com/synhershko/> On Sat, Jan 11, 2014 at 7:36 PM, Nate Fox <[email protected]> wrote: > Is there a way to tell a node to remove all of its data (spread it back > out among the other nodes) so that I can shut it down and not deal with a > rebalance/re-replicate once its down? > > If I have 2 copies of each shard and I drop one node, some of the shards > now only have 1 live copy and it has to be re-replicated. I'd prefer to not > drop down to 1 live copy for any period of time if I can avoid it. > > -- > 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/1268eb38-a4df-42f5-81cf-29180c768916%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- 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/CAHTr4ZtP%2BOh_rVQ6FYzWny0w7zggrZ7b%2Bs1%3DvAuZr%2BZW%2Bp%2B2Gg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
