# ES 6.2.3 cluster goes down unexpectedly

**URL:** <https://discuss.elastic.co/t/es-6-2-3-cluster-goes-down-unexpectedly/131292>\
**Category:** Elasticsearch\
**Created:** [May 10, 2018, 11:06am UTC](https://discuss.elastic.co/t/es-6-2-3-cluster-goes-down-unexpectedly/131292 "2018-05-10T11:06:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![renjith\_ravindran](https://avatars.discourse-cdn.com/v4/letter/r/5f9b8f/32.png) [@renjith\_ravindran](https://discuss.elastic.co/u/renjith_ravindran)\
**Post date:** [May 10, 2018, 11:06am UTC](https://discuss.elastic.co/t/es-6-2-3-cluster-goes-down-unexpectedly/131292/1 "2018-05-10T11:06:01Z")

</div>

I have a cluster with 2 co-ordinate nodes and 4 data/master nodes.  
(1 coordinate node and 2 data/master node in each DC)

I have not started indexing any data, and even index is not created yet. But still the cluster goes down unexpectedly and I am seeing a lot of connect errors in logs.

network.host: 0.0.0.0  
http.port: 9200  
discovery.zen.minimum\_master\_nodes: 2  
discovery.zen.ping\_timeout: 30s  
bootstrap.memory\_lock: true  
node.master: false  
node.ingest: false  
node.data: false  
cluster.routing.allocation.awareness.attributes: dc  
transport.publish\_host: 10.60.1XX.XX  
node.name: ivylx3601  
node.attr.dc: ttc  
discovery.zen.ping.unicast.hosts:

- 10.60.1XX.XX ( coordinate)

- 10.60.2XX.XX

- 10.60.3XX.XX

- 10.61.1XX.XX( coordinate)

- 10.61.2XX.XX

- 10.61.3XX.XX

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 10, 2018, 11:12am UTC](https://discuss.elastic.co/t/es-6-2-3-cluster-goes-down-unexpectedly/131292/2 "2018-05-10T11:12:50Z")

</div>

> [@renjith\_ravindran](#):
>
> discovery.zen.minimum\_master\_nodes: 2

If you have 4 master/data nodes, this should be set to `3` (not `2`) as per [these guidelines](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/modules-node.html#split-brain) in order to avoid split-brain scenarios.

How far apart are the two DCs? Elasticsearch required good bandwidth and low latency between nodes, so deployments across multiple DCs that are not very close and well connected is not recommended.

---

<div class="post-metadata">

**Author:** ![renjith\_ravindran](https://avatars.discourse-cdn.com/v4/letter/r/5f9b8f/32.png) [@renjith\_ravindran](https://discuss.elastic.co/u/renjith_ravindran)\
**Post date:** [May 10, 2018, 11:21am UTC](https://discuss.elastic.co/t/es-6-2-3-cluster-goes-down-unexpectedly/131292/3 "2018-05-10T11:21:04Z")

</div>

We have put it as 3 purposefully in order to avoid the situation where one DC goes down. The DC connectivity is stable and have high bandwidth as well

---

<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:** [June 7, 2018, 11:21am UTC](https://discuss.elastic.co/t/es-6-2-3-cluster-goes-down-unexpectedly/131292/4 "2018-06-07T11:21:07Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.