# Restarting a 2-node elasticsearch cluster with zero downtime **URL:** \ **Category:** Elasticsearch\ **Created:** [December 7, 2014, 5:38pm UTC](https://discuss.elastic.co/t/restarting-a-2-node-elasticsearch-cluster-with-zero-downtime/21126 "2014-12-07T17:38:23Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Nariman\_Haghighi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nariman_haghighi/32/1065_2.png) [@Nariman\_Haghighi](https://discuss.elastic.co/u/Nariman_Haghighi)\ **Post date:** [December 7, 2014, 5:38pm UTC](https://discuss.elastic.co/t/restarting-a-2-node-elasticsearch-cluster-with-zero-downtime/21126/1 "2014-12-07T17:38:23Z")
Cross-posting from stackoverflow: > Not sure when this behaviour changed but it seems odd that you can't force an immediate election when you explicitly shutdown a master. And the guidance around what happens in this "no master block [http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html)" scenario seems off based on what we're experiencing: Read operations will succeed, based on the last known cluster > configuration. This may result in partial reads of stale data as this node > may be isolated from the rest of the cluster. -- 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/65284942-51de-44f1-ab4f-fed77d905c8a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/65284942-51de-44f1-ab4f-fed77d905c8a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Nariman\_Haghighi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nariman_haghighi/32/1065_2.png) [@Nariman\_Haghighi](https://discuss.elastic.co/u/Nariman_Haghighi)\ **Post date:** [December 8, 2014, 9:41pm UTC](https://discuss.elastic.co/t/restarting-a-2-node-elasticsearch-cluster-with-zero-downtime/21126/2 "2014-12-08T21:41:42Z")
We've gathered more information here and updated the question below but the question still stands: Shouldn't there be a way to avoid a "no master block" during a cluster restart when the master is explicitly shutdown? On Sunday, December 7, 2014 12:38:23 PM UTC-5, Nariman Haghighi wrote: > Cross-posting from stackoverflow: > > [Restarting a 2-node elasticsearch cluster with zero downtime - Stack Overflow](http://stackoverflow.com/questions/27345508/restarting-a-2-node-elasticsearch-cluster-with-zero-downtime) > > Not sure when this behaviour changed but it seems odd that you can't force > an immediate election when you explicitly shutdown a master. > > And the guidance around what happens in this "no master block > [http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html)" > scenario seems off based on what we're experiencing: > > Read operations will succeed, based on the last known cluster > > > configuration. This may result in partial reads of stale data as this node > > may be isolated from the rest of the cluster. -- 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/23a3a103-dedc-4c31-b079-e49e3c35eac2%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/23a3a103-dedc-4c31-b079-e49e3c35eac2%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:44am UTC](https://discuss.elastic.co/t/restarting-a-2-node-elasticsearch-cluster-with-zero-downtime/21126/3 "2017-07-06T00:44:52Z")