# Decommission of multiple nodes

**URL:** https://discuss.elastic.co/t/decommission-of-multiple-nodes/21036
**Category:** Elasticsearch
**Created:** [December 2, 2014, 4:01pm UTC](https://discuss.elastic.co/t/decommission-of-multiple-nodes/21036 "2014-12-02T16:01:14Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Noam\_Gazit](https://avatars.discourse-cdn.com/v4/letter/n/df705f/32.png) [@Noam\_Gazit](https://discuss.elastic.co/u/Noam_Gazit)
#### Post date: [December 2, 2014, 4:01pm UTC](https://discuss.elastic.co/t/decommission-of-multiple-nodes/21036/1 "2014-12-02T16:01:14Z")

</div>

Hi,

I wanted to reduce my cluster size by 3 data nodes (from 27 to 24).  
I issued 3 decommission API calls one after the other and saw their shards  
start moving.  
I waited for all the shards to relocate, but when I checked to make sure  
they can safely be removed I found out that they have new shards on them.

Is there a limit to the number of nodes that can be decommissioned at the  
same time?  
Is there a timeout for the decommission definition for a node?  
Anything else?

Thanks for the help,  
Noam

--  
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/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [December 2, 2014, 9:00pm UTC](https://discuss.elastic.co/t/decommission-of-multiple-nodes/21036/2 "2014-12-02T21:00:16Z")

</div>

What do you mean by decommission, there is no API call for that, unless you  
meant shutdown?

The easiest way would be to power down one node at a time, waiting for  
things to rebalance before shutting another down.

On 3 December 2014 at 03:01, Noam Gazit [noam@totango.com](mailto:noam@totango.com) wrote:

> Hi,
> 
> I wanted to reduce my cluster size by 3 data nodes (from 27 to 24).  
> I issued 3 decommission API calls one after the other and saw their shards  
> start moving.  
> I waited for all the shards to relocate, but when I checked to make sure  
> they can safely be removed I found out that they have new shards on them.
> 
> Is there a limit to the number of nodes that can be decommissioned at the  
> same time?  
> Is there a timeout for the decommission definition for a node?  
> Anything else?
> 
> Thanks for the help,  
> Noam
> 
> --  
> 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/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CAEYi1X8%3DLa7uK-Aiykx5Xkm0hy3-dLuY7L\_0QOzLRzApCxHQGg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8%3DLa7uK-Aiykx5Xkm0hy3-dLuY7L_0QOzLRzApCxHQGg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)
#### Post date: [December 2, 2014, 9:05pm UTC](https://discuss.elastic.co/t/decommission-of-multiple-nodes/21036/3 "2014-12-02T21:05:24Z")

</div>

If you mean allocation filtering (like  
cluster.routing.allocation.exclude.\_ip) then you just need to specify all  
three ip addresses with commas between them.

Nik

On Tue, Dec 2, 2014 at 4:00 PM, Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com) wrote:

> What do you mean by decommission, there is no API call for that, unless  
> you meant shutdown?
> 
> The easiest way would be to power down one node at a time, waiting for  
> things to rebalance before shutting another down.
> 
> On 3 December 2014 at 03:01, Noam Gazit [noam@totango.com](mailto:noam@totango.com) wrote:
> 
> > Hi,
> > 
> > I wanted to reduce my cluster size by 3 data nodes (from 27 to 24).  
> > I issued 3 decommission API calls one after the other and saw their  
> > shards start moving.  
> > I waited for all the shards to relocate, but when I checked to make sure  
> > they can safely be removed I found out that they have new shards on them.
> > 
> > Is there a limit to the number of nodes that can be decommissioned at the  
> > same time?  
> > Is there a timeout for the decommission definition for a node?  
> > Anything else?
> > 
> > Thanks for the help,  
> > Noam
> > 
> > --  
> > 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/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> 
> --  
> 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/CAEYi1X8%3DLa7uK-Aiykx5Xkm0hy3-dLuY7L\_0QOzLRzApCxHQGg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8%3DLa7uK-Aiykx5Xkm0hy3-dLuY7L_0QOzLRzApCxHQGg%40mail.gmail.com)  
> [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8%3DLa7uK-Aiykx5Xkm0hy3-dLuY7L\_0QOzLRzApCxHQGg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8%3DLa7uK-Aiykx5Xkm0hy3-dLuY7L_0QOzLRzApCxHQGg%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> .
> 
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CAPmjWd1i8H%3D6A4utfWh7EVSDg\_OK6RdvHDKVgkWXfFEeOt%2BG1g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1i8H%3D6A4utfWh7EVSDg_OK6RdvHDKVgkWXfFEeOt%2BG1g%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![Ye\_D](https://avatars.discourse-cdn.com/v4/letter/y/ccd318/32.png) [@Ye\_D](https://discuss.elastic.co/u/Ye_D)
#### Post date: [December 17, 2014, 11:03pm UTC](https://discuss.elastic.co/t/decommission-of-multiple-nodes/21036/4 "2014-12-17T23:03:36Z")

</div>

Hi Nik,

I found the that I am not able to do decommissioning over multiple nodes.  
I can do decommissioning over a single node.

These cmds below work perfectly for my ES cluster:  
"cluster.routing.allocation.exclude.\_name": "node-1"  
"cluster.routing.allocation.exclude.\_name": "node-2"  
"cluster.routing.allocation.exclude.\_ip": "ip1"  
"cluster.routing.allocation.exclude.\_ip": "ip2"

But none of these cmds below has effect for my ES cluster:  
"cluster.routing.allocation.exclude.\_name": "node-1,node-2"  
"cluster.routing.allocation.exclude.\_name": ["node-1", "node-2"]  
"cluster.routing.allocation.exclude.\_ip": "ip1,ip2"  
"cluster.routing.allocation.exclude.\_ip": "ip1, ip2"

I also notice that extra spaces for "\_name" or "\_ip" field cause the cmd to  
fail (no effect).  
For example, none of these cmds below works.  
"cluster.routing.allocation.exclude.\_ip": " ip1 "  
"cluster.routing.allocation.exclude.\_name": "node-1 "

I am running this version of ES on Ubuntu 14.04:

> elasticsearch -v  
> Version: 1.4.0, Build: bc94bd8/2014-11-05T14:26:12Z, JVM: 1.8.0\_25

I checked release notes of ES 1.4.1 and 1.4.2, and I didn't find some bug  
fixing notes for this "decommissioning over multiple nodes" function.

Is this a bug? Or, I omit something important?

Regards,  
Ye

On Tuesday, December 2, 2014 4:07:15 PM UTC-5, Nikolas Everett wrote:

> If you mean allocation filtering (like  
> cluster.routing.allocation.exclude.\_ip) then you just need to specify all  
> three ip addresses with commas between them.
> 
> Nik
> 
> On Tue, Dec 2, 2014 at 4:00 PM, Mark Walkom \<[markw...@gmail.com](mailto:markw...@gmail.com)  
> \<javascript:\>\> wrote:
> 
> > What do you mean by decommission, there is no API call for that, unless  
> > you meant shutdown?
> > 
> > The easiest way would be to power down one node at a time, waiting for  
> > things to rebalance before shutting another down.
> > 
> > On 3 December 2014 at 03:01, Noam Gazit \<[no...@totango.com](mailto:no...@totango.com) \<javascript:\>\>  
> > wrote:
> > 
> > > Hi,
> > > 
> > > I wanted to reduce my cluster size by 3 data nodes (from 27 to 24).  
> > > I issued 3 decommission API calls one after the other and saw their  
> > > shards start moving.  
> > > I waited for all the shards to relocate, but when I checked to make sure  
> > > they can safely be removed I found out that they have new shards on them.
> > > 
> > > Is there a limit to the number of nodes that can be decommissioned at  
> > > the same time?  
> > > Is there a timeout for the decommission definition for a node?  
> > > Anything else?
> > > 
> > > Thanks for the help,  
> > > Noam
> > > 
> > > --  
> > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > > To view this discussion on the web visit  
> > > [https://groups.google.com/d/msgid/elasticsearch/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/86afdf02-3dff-4495-a555-8f70f9356216%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > > .  
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > 
> > --  
> > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8%3DLa7uK-Aiykx5Xkm0hy3-dLuY7L\_0QOzLRzApCxHQGg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8%3DLa7uK-Aiykx5Xkm0hy3-dLuY7L_0QOzLRzApCxHQGg%40mail.gmail.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8%3DLa7uK-Aiykx5Xkm0hy3-dLuY7L\_0QOzLRzApCxHQGg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X8%3DLa7uK-Aiykx5Xkm0hy3-dLuY7L_0QOzLRzApCxHQGg%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> > .
> > 
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/820fb54b-d932-4a7f-8ee5-906b88a5e2b3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/820fb54b-d932-4a7f-8ee5-906b88a5e2b3%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### Author: ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)
#### Post date: [December 17, 2014, 11:10pm UTC](https://discuss.elastic.co/t/decommission-of-multiple-nodes/21036/5 "2014-12-17T23:10:49Z")

</div>

On Wed, Dec 17, 2014 at 6:03 PM, Ye D [ye@volarvideo.com](mailto:ye@volarvideo.com) wrote:

> "cluster.routing.allocation.exclude.\_ip": "ip1, ip2"

I use this one and I'm pretty sure its worked for me in the past.

Nik

--  
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/CAPmjWd3\_DpdkrMgGMiNGJEaorhc55N3znc9Wx%2BA2HC%2BocHFJ0A%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3_DpdkrMgGMiNGJEaorhc55N3znc9Wx%2BA2HC%2BocHFJ0A%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

### 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, 12:43am UTC](https://discuss.elastic.co/t/decommission-of-multiple-nodes/21036/6 "2017-07-06T00:43:03Z")

</div>


