# Planned total network page - how will the cluster react? **URL:** \ **Category:** Elasticsearch\ **Created:** [June 28, 2021, 1:54pm UTC](https://discuss.elastic.co/t/planned-total-network-page-how-will-the-cluster-react/277235 "2021-06-28T13:54:08Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![ankh](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@ankh](https://discuss.elastic.co/u/ankh)\ **Post date:** [June 28, 2021, 1:54pm UTC](https://discuss.elastic.co/t/planned-total-network-page-how-will-the-cluster-react/277235/1 "2021-06-28T13:54:08Z")
We have a planned network outage for 8 hours that will stop communication between all hosts, including between nodes in our elastic cluster. We have 3 master nodes and 2 minimum master nodes set. Using logstash to write to the cluster and apps read from it. Indexes are replicated with 1p, 2r. I don't want to have to organise for the cluster to be shut down and restarted. If I do nothing, will the cluster have any problems? I didn't think it would, apart from maybe lots of errors being logged. But should I be cautious, and stop the logstash jobs, and maybe set shard allocation to a long period to cover the outage? Or something else? Not really sure what is best. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [June 28, 2021, 2:25pm UTC](https://discuss.elastic.co/t/planned-total-network-page-how-will-the-cluster-react/277235/2 "2021-06-28T14:25:04Z")
What version are you using? The cluster won't work while the network is broken but it should recover on its own when connectivity is restored. You don't need to do anything special to make that happen, but I suppose it might help it recover a bit quicker if you set `cluster.routing.allocation.enable: none` beforehand and then remove this setting once the outage is over. I don't know how Logstash will react to the cluster being unavailable and/or rejecting its writes. Best to ask that again in the Logstash forum. ---
**Author:** ![ankh](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@ankh](https://discuss.elastic.co/u/ankh)\ **Post date:** [June 28, 2021, 11:05pm UTC](https://discuss.elastic.co/t/planned-total-network-page-how-will-the-cluster-react/277235/3 "2021-06-28T23:05:28Z")
Thanks very much for your reply David. We're on version 6.2.3. ---
**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:** [June 29, 2021, 1:40am UTC](https://discuss.elastic.co/t/planned-total-network-page-how-will-the-cluster-react/277235/4 "2021-06-29T01:40:54Z")
Tangential, but please upgrade as 6.2 reached [EOL](https://www.elastic.co/support/eol) 2 years ago. ---
**Author:** ![ankh](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@ankh](https://discuss.elastic.co/u/ankh)\ **Post date:** [June 29, 2021, 3:10am UTC](https://discuss.elastic.co/t/planned-total-network-page-how-will-the-cluster-react/277235/5 "2021-06-29T03:10:07Z")
Yes, that's definitely something we need to do, getting such work prioritised is difficult, even though the longer we wait the harder it will get. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 27, 2021, 3:11am UTC](https://discuss.elastic.co/t/planned-total-network-page-how-will-the-cluster-react/277235/6 "2021-07-27T03:11:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.