# Is it required to restart the routing/coordinator process when data node disconnects from network and comes back?

**URL:** <https://discuss.elastic.co/t/is-it-required-to-restart-the-routing-coordinator-process-when-data-node-disconnects-from-network-and-comes-back/44908>\
**Category:** Elasticsearch\
**Created:** [March 19, 2016, 7:51pm UTC](https://discuss.elastic.co/t/is-it-required-to-restart-the-routing-coordinator-process-when-data-node-disconnects-from-network-and-comes-back/44908 "2016-03-19T19:51:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dany](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dany/32/8131_2.png) [@dany](https://discuss.elastic.co/u/dany)\
**Post date:** [March 19, 2016, 7:51pm UTC](https://discuss.elastic.co/t/is-it-required-to-restart-the-routing-coordinator-process-when-data-node-disconnects-from-network-and-comes-back/44908/1 "2016-03-19T19:51:16Z")

</div>

I know this could have been discussed in several posts. But I couldn't find a solution yet. This happens in few cases[not always]. When a data node moves out of the network and comes back, it is not getting registered to cluster automatically. I end up restarting the routing node process to identify the data node

Is it required to restart the routing/coordinator process when data node disconnects from network and comes back?  
Or is there any setting I can change to increase the number of checks from cluster for new nodes when a node goes out of network?

---

<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:** [March 19, 2016, 11:33pm UTC](https://discuss.elastic.co/t/is-it-required-to-restart-the-routing-coordinator-process-when-data-node-disconnects-from-network-and-comes-back/44908/2 "2016-03-19T23:33:39Z")

</div>

It shouldn't need a restart, no.  
Assuming you are using zen discovery, take a look at [https://www.elastic.co/guide/en/elasticsearch/reference/2.2/modules-discovery-zen.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.2/modules-discovery-zen.html)

---

<div class="post-metadata">

**Author:** ![dany](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dany/32/8131_2.png) [@dany](https://discuss.elastic.co/u/dany)\
**Post date:** [March 22, 2016, 8:24pm UTC](https://discuss.elastic.co/t/is-it-required-to-restart-the-routing-coordinator-process-when-data-node-disconnects-from-network-and-comes-back/44908/3 "2016-03-22T20:24:14Z")

</div>

Thanks for the response. I use zen discovery. I only use the zen minimum\_master\_nodes settings in the config.

zen:  
minimum\_master\_nodes: 2

Do I need set the ping\_retries[default to 3] setting if the network failure exists for more than the default retries time 90s. [3 \* ping\_timeout = 3 \* 30s = 90s]

I mean set ping\_retries to a higher value [eg. 10 or 20].  
So the node will join back in case if the network failure exists for 10 mins with  
ping\_retries : 20  
ping\_timeout:30s

---

<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 5, 2017, 11:06pm UTC](https://discuss.elastic.co/t/is-it-required-to-restart-the-routing-coordinator-process-when-data-node-disconnects-from-network-and-comes-back/44908/4 "2017-07-05T23:06:09Z")

</div>