# Next steps... how to reboot a node without starting a re-balance of unallocated shards
**URL:** https://discuss.elastic.co/t/next-steps-how-to-reboot-a-node-without-starting-a-re-balance-of-unallocated-shards/14875
**Category:** Elasticsearch
**Created:** [December 16, 2013, 12:31am UTC](https://discuss.elastic.co/t/next-steps-how-to-reboot-a-node-without-starting-a-re-balance-of-unallocated-shards/14875 "2013-12-16T00:31:38Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Aaron\_Anderson](https://discuss.elastic.co/u/Aaron_Anderson)
#### Post date: [December 16, 2013, 12:31am UTC](https://discuss.elastic.co/t/next-steps-how-to-reboot-a-node-without-starting-a-re-balance-of-unallocated-shards/14875/1 "2013-12-16T00:31:38Z")
I have a 4 node cluster. (just a proof of concept right now, but will
potentially consume 100gb+ per day)
What configuration items do I need to learn/read about to delay
re-balancing of unallocated shards? For example, I am required to do system
patching on a regular basis, so each node is going to have to go through a
reboot. How can I reboot the host, or restart ES for new settings to take
effect, without kicking off the re-balance?
Can I somehow specify a delay? My current config is posted below.
ALSO: I notice (in the head plugin) if I do a "service elasticsearch
restart" on a node that I will end up with two nodes with the same address
each holding different shards, probably because in the short time the node
was down that particular shard wasn't moved somewhere else. Is this OK? For
example, if i restart LouDvEs001 (which is the address, names are auto gen)
I'll have two nodes with different names, but the same address.
cluster:
name: dvlogstash
discovery:
zen:
minimum\_master\_nodes: 2
ping:
multicast:
enabled: false
unicast:
hosts:
- loudves001
- loudves002
- loudves003
- loudves004
path:
conf: /etc/elasticsearch/
logs: /var/log/elasticsearch/
--
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/8b7f59db-50fe-4df2-9f18-167d66fccab7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8b7f59db-50fe-4df2-9f18-167d66fccab7%40googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [December 16, 2013, 12:56am UTC](https://discuss.elastic.co/t/next-steps-how-to-reboot-a-node-without-starting-a-re-balance-of-unallocated-shards/14875/2 "2013-12-16T00:56:12Z")
cluster.routing.allocation.disable\_allocation is probably what you want.
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
On 16 December 2013 11:31, Aaron Anderson [anderson.aaron@gmail.com](mailto:anderson.aaron@gmail.com) wrote:
> I have a 4 node cluster. (just a proof of concept right now, but will
> potentially consume 100gb+ per day)
>
> What configuration items do I need to learn/read about to delay
> re-balancing of unallocated shards? For example, I am required to do system
> patching on a regular basis, so each node is going to have to go through a
> reboot. How can I reboot the host, or restart ES for new settings to take
> effect, without kicking off the re-balance?
>
> Can I somehow specify a delay? My current config is posted below.
>
> ALSO: I notice (in the head plugin) if I do a "service elasticsearch
> restart" on a node that I will end up with two nodes with the same address
> each holding different shards, probably because in the short time the node
> was down that particular shard wasn't moved somewhere else. Is this OK? For
> example, if i restart LouDvEs001 (which is the address, names are auto gen)
> I'll have two nodes with different names, but the same address.
>
> cluster:
> name: dvlogstash
> discovery:
> zen:
> minimum\_master\_nodes: 2
> ping:
> multicast:
> enabled: false
> unicast:
> hosts:
> - loudves001
> - loudves002
> - loudves003
> - loudves004
> path:
> conf: /etc/elasticsearch/
> logs: /var/log/elasticsearch/
>
> --
> 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/8b7f59db-50fe-4df2-9f18-167d66fccab7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8b7f59db-50fe-4df2-9f18-167d66fccab7%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/CAEM624bsBStCWZ%2BA6e13V3LbSNGztPbNGhPuQA26NeMKwMhDLQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624bsBStCWZ%2BA6e13V3LbSNGztPbNGhPuQA26NeMKwMhDLQ%40mail.gmail.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@Ivan](https://discuss.elastic.co/u/Ivan)
#### Post date: [December 17, 2013, 4:38am UTC](https://discuss.elastic.co/t/next-steps-how-to-reboot-a-node-without-starting-a-re-balance-of-unallocated-shards/14875/3 "2013-12-17T04:38:25Z")
Besides what Mark mentioned (the key setting to use), the only other thing
I can suggest is to flush the transaction log before rebooting any node
(assuming you can disable indexing and allocation).
Cheers,
Ivan
On Sun, Dec 15, 2013 at 4:56 PM, Mark Walkom [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)wrote:
> cluster.routing.allocation.disable\_allocation is probably what you want.
>
> Regards,
> Mark Walkom
>
> Infrastructure Engineer
> Campaign Monitor
> email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)
> web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
>
> On 16 December 2013 11:31, Aaron Anderson [anderson.aaron@gmail.com](mailto:anderson.aaron@gmail.com)wrote:
>
> > I have a 4 node cluster. (just a proof of concept right now, but will
> > potentially consume 100gb+ per day)
> >
> > What configuration items do I need to learn/read about to delay
> > re-balancing of unallocated shards? For example, I am required to do system
> > patching on a regular basis, so each node is going to have to go through a
> > reboot. How can I reboot the host, or restart ES for new settings to take
> > effect, without kicking off the re-balance?
> >
> > Can I somehow specify a delay? My current config is posted below.
> >
> > ALSO: I notice (in the head plugin) if I do a "service elasticsearch
> > restart" on a node that I will end up with two nodes with the same address
> > each holding different shards, probably because in the short time the node
> > was down that particular shard wasn't moved somewhere else. Is this OK? For
> > example, if i restart LouDvEs001 (which is the address, names are auto gen)
> > I'll have two nodes with different names, but the same address.
> >
> > cluster:
> > name: dvlogstash
> > discovery:
> > zen:
> > minimum\_master\_nodes: 2
> > ping:
> > multicast:
> > enabled: false
> > unicast:
> > hosts:
> > - loudves001
> > - loudves002
> > - loudves003
> > - loudves004
> > path:
> > conf: /etc/elasticsearch/
> > logs: /var/log/elasticsearch/
> >
> > --
> > 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/8b7f59db-50fe-4df2-9f18-167d66fccab7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8b7f59db-50fe-4df2-9f18-167d66fccab7%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/CAEM624bsBStCWZ%2BA6e13V3LbSNGztPbNGhPuQA26NeMKwMhDLQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624bsBStCWZ%2BA6e13V3LbSNGztPbNGhPuQA26NeMKwMhDLQ%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/CALY%3DcQCBRiRzfy70MkPHNZ5wFk9C3N%2BueH6C3UmOpX5j0tw-vg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQCBRiRzfy70MkPHNZ5wFk9C3N%2BueH6C3UmOpX5j0tw-vg%40mail.gmail.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 2:00am UTC](https://discuss.elastic.co/t/next-steps-how-to-reboot-a-node-without-starting-a-re-balance-of-unallocated-shards/14875/4 "2017-07-06T02:00:46Z")