# Evacuate data off of a node? **URL:** \ **Category:** Elasticsearch\ **Created:** [January 11, 2014, 5:36pm UTC](https://discuss.elastic.co/t/evacuate-data-off-of-a-node/15209 "2014-01-11T17:36:51Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![natefox](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/natefox/32/44821_2.png) [@natefox](https://discuss.elastic.co/u/natefox)\ **Post date:** [January 11, 2014, 5:36pm UTC](https://discuss.elastic.co/t/evacuate-data-off-of-a-node/15209/1 "2014-01-11T17:36:51Z")
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1268eb38-a4df-42f5-81cf-29180c768916%40googlegroups.com](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](https://groups.google.com/groups/opt_out). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [January 11, 2014, 5:39pm UTC](https://discuss.elastic.co/t/evacuate-data-off-of-a-node/15209/2 "2014-01-11T17:39:07Z")
The cluster.routing.allocation.exclude.\_ip config - see > **[ElasticSearch Shard Placement Control - Sematext](https://sematext.com/blog/elasticsearch-shard-placement-control/)** > > In this post you will learn how to control ElasticSearch shard placement.  If you are coming to our ElasticSearch talk at BerlinBuzzwords, we’ll be talking about this and more. If you’ve ever used ElasticSearch you probably know that you can set... -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Sat, Jan 11, 2014 at 7:36 PM, Nate Fox [thefox@gmail.com](mailto:thefox@gmail.com) 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/1268eb38-a4df-42f5-81cf-29180c768916%40googlegroups.com](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](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). 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](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](https://groups.google.com/groups/opt_out). ---
**Author:** ![natefox](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/natefox/32/44821_2.png) [@natefox](https://discuss.elastic.co/u/natefox)\ **Post date:** [January 11, 2014, 5:46pm UTC](https://discuss.elastic.co/t/evacuate-data-off-of-a-node/15209/3 "2014-01-11T17:46:19Z")
Thank you. Somehow my googling never brought up the existing topics on that. From the docs, I see I can do the following: curl -XPUT localhost:9200/\_cluster/settings -d '{ "transient" : { "cluster.routing.allocation.exclude.\_ip" : "10.0.0.1" } }' However, what do I do to 're-allow' the IP? Do I use the .include.\_ip or do I set the .exclude.\_ip string to ""? On Sat, Jan 11, 2014 at 9:39 AM, Itamar Syn-Hershko [itamar@code972.com](mailto:itamar@code972.com)wrote: > The cluster.routing.allocation.exclude.\_ip config - see > [ElasticSearch Shard Placement Control - Sematext](http://blog.sematext.com/2012/05/29/elasticsearch-shard-placement-control/) > > -- > > Itamar Syn-Hershko > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > Freelance Developer & Consultant > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > On Sat, Jan 11, 2014 at 7:36 PM, Nate Fox [thefox@gmail.com](mailto:thefox@gmail.com) 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/1268eb38-a4df-42f5-81cf-29180c768916%40googlegroups.com](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](https://groups.google.com/groups/opt_out). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/7lq7d\_0q\_qg/unsubscribe](https://groups.google.com/d/topic/elasticsearch/7lq7d_0q_qg/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > 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](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](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHU4sP9PA98RN%3Dn24diEACKHm9PahbjBfuMKG6U-Pirnqgk1fA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHU4sP9PA98RN%3Dn24diEACKHm9PahbjBfuMKG6U-Pirnqgk1fA%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [January 11, 2014, 5:47pm UTC](https://discuss.elastic.co/t/evacuate-data-off-of-a-node/15209/4 "2014-01-11T17:47:57Z")
You update the exclude setting to remove that IP, usually -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Sat, Jan 11, 2014 at 7:46 PM, Nate Fox [thefox@gmail.com](mailto:thefox@gmail.com) wrote: > Thank you. Somehow my googling never brought up the existing topics on > that. > From the docs, I see I can do the following: > > curl -XPUT localhost:9200/\_cluster/settings -d '{ > "transient" : { > "cluster.routing.allocation.exclude.\_ip" : "10.0.0.1" > } > }' > > However, what do I do to 're-allow' the IP? Do I use the .include.\_ip or > do I set the .exclude.\_ip string to ""? > > On Sat, Jan 11, 2014 at 9:39 AM, Itamar Syn-Hershko [itamar@code972.com](mailto:itamar@code972.com)wrote: > > > The cluster.routing.allocation.exclude.\_ip config - see > > [ElasticSearch Shard Placement Control - Sematext](http://blog.sematext.com/2012/05/29/elasticsearch-shard-placement-control/) > > > > -- > > > > Itamar Syn-Hershko > > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > > Freelance Developer & Consultant > > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > > > On Sat, Jan 11, 2014 at 7:36 PM, Nate Fox [thefox@gmail.com](mailto:thefox@gmail.com) 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/1268eb38-a4df-42f5-81cf-29180c768916%40googlegroups.com](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](https://groups.google.com/groups/opt_out). > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/7lq7d\_0q\_qg/unsubscribe](https://groups.google.com/d/topic/elasticsearch/7lq7d_0q_qg/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > 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](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](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAHU4sP9PA98RN%3Dn24diEACKHm9PahbjBfuMKG6U-Pirnqgk1fA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHU4sP9PA98RN%3Dn24diEACKHm9PahbjBfuMKG6U-Pirnqgk1fA%40mail.gmail.com) > . > > For more options, visit [https://groups.google.com/groups/opt\_out](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZuXd7%3Doby1WnueVWdhhwhAUVvUNrFrpfd9d22Lnso3x%2BA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZuXd7%3Doby1WnueVWdhhwhAUVvUNrFrpfd9d22Lnso3x%2BA%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![natefox](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/natefox/32/44821_2.png) [@natefox](https://discuss.elastic.co/u/natefox)\ **Post date:** [January 11, 2014, 7:57pm UTC](https://discuss.elastic.co/t/evacuate-data-off-of-a-node/15209/5 "2014-01-11T19:57:37Z")
This worked perfectly. Thank you! On Sat, Jan 11, 2014 at 9:47 AM, Itamar Syn-Hershko [itamar@code972.com](mailto:itamar@code972.com)wrote: > You update the exclude setting to remove that IP, usually > > -- > > Itamar Syn-Hershko > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > Freelance Developer & Consultant > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > On Sat, Jan 11, 2014 at 7:46 PM, Nate Fox [thefox@gmail.com](mailto:thefox@gmail.com) wrote: > > > Thank you. Somehow my googling never brought up the existing topics on > > that. > > From the docs, I see I can do the following: > > > > curl -XPUT localhost:9200/\_cluster/settings -d '{ > > "transient" : { > > "cluster.routing.allocation.exclude.\_ip" : "10.0.0.1" > > } > > }' > > > > However, what do I do to 're-allow' the IP? Do I use the .include.\_ip or > > do I set the .exclude.\_ip string to ""? > > > > On Sat, Jan 11, 2014 at 9:39 AM, Itamar Syn-Hershko [itamar@code972.com](mailto:itamar@code972.com)wrote: > > > > > The cluster.routing.allocation.exclude.\_ip config - see > > > [ElasticSearch Shard Placement Control - Sematext](http://blog.sematext.com/2012/05/29/elasticsearch-shard-placement-control/) > > > > > > -- > > > > > > Itamar Syn-Hershko > > > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > > > Freelance Developer & Consultant > > > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > > > > > On Sat, Jan 11, 2014 at 7:36 PM, Nate Fox [thefox@gmail.com](mailto:thefox@gmail.com) 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > > > > > To view this discussion on the web visit > > > > [https://groups.google.com/d/msgid/elasticsearch/1268eb38-a4df-42f5-81cf-29180c768916%40googlegroups.com](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](https://groups.google.com/groups/opt_out). > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/7lq7d\_0q\_qg/unsubscribe](https://groups.google.com/d/topic/elasticsearch/7lq7d_0q_qg/unsubscribe). > > > To unsubscribe from this group and all its topics, send an email to > > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > 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](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](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CAHU4sP9PA98RN%3Dn24diEACKHm9PahbjBfuMKG6U-Pirnqgk1fA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHU4sP9PA98RN%3Dn24diEACKHm9PahbjBfuMKG6U-Pirnqgk1fA%40mail.gmail.com) > > . > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/7lq7d\_0q\_qg/unsubscribe](https://groups.google.com/d/topic/elasticsearch/7lq7d_0q_qg/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZuXd7%3Doby1WnueVWdhhwhAUVvUNrFrpfd9d22Lnso3x%2BA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZuXd7%3Doby1WnueVWdhhwhAUVvUNrFrpfd9d22Lnso3x%2BA%40mail.gmail.com) > . > > For more options, visit [https://groups.google.com/groups/opt\_out](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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAHU4sP8wKxJawSif0TGhsHZmETUMxL10K%3DxTy%3D54OkaH7\_9EkQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHU4sP8wKxJawSif0TGhsHZmETUMxL10K%3DxTy%3D54OkaH7_9EkQ%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:57am UTC](https://discuss.elastic.co/t/evacuate-data-off-of-a-node/15209/6 "2017-07-06T01:57:16Z")