# Elk loses contact with the master every morning at 8am and the cluster turns red

**URL:** <https://discuss.elastic.co/t/elk-loses-contact-with-the-master-every-morning-at-8am-and-the-cluster-turns-red/343621>\
**Category:** Elasticsearch\
**Created:** [September 22, 2023, 1:09pm UTC](https://discuss.elastic.co/t/elk-loses-contact-with-the-master-every-morning-at-8am-and-the-cluster-turns-red/343621 "2023-09-22T13:09:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![abcdbdocker](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abcdbdocker/32/125916_2.png) [@abcdbdocker](https://discuss.elastic.co/u/abcdbdocker)\
**Post date:** [September 22, 2023, 1:09pm UTC](https://discuss.elastic.co/t/elk-loses-contact-with-the-master-every-morning-at-8am-and-the-cluster-turns-red/343621/1 "2023-09-22T13:09:48Z")

</div>

重点词汇  
690/5000  
传统翻译模型  
通用场景  
hello Our cluster will turn red after 8 am every day. The cluster size is 6 hot data nodes 3 warm data nodes. The primary node is the same as the hot data node. Recently, we found a strange phenomenon that the cluster status will turn red at 8:12 every day View master logs :[esdata01] current.health="RED" message="Cluster health status changed from [GREEN] to [RED] (reason: [{esdata09}{\_gbguhWlS0OxedNrcCIUgQ}{Dxtoj4WYSjGBROPS9mpHcQ}{esdata09}{sw}{8.8.2} reason: {{esdata09}{\_GBguhwLS0OxedNrcciugQ}{DXtoj4WysjGbrops9mphCq}{esdata09}{SW}{8.8.2} lagging, {esdata07}{HNptjVxORhe0mU--i0km6g}{l8kuExZ-Sz-okJdIltZP7Q}{esdata07}{sw}{8.8.2} reason: lagging])." previous.health="GREEN" reason="{esdata09}{\_gbguhWlS0OxedNrcCIUgQ}{Dxtoj4WYSjGBROPS9mpHcQ}{esdata09}{sw}{8.8.2} reason: {esdata09}{\_GBGuhwLS0OxedNrcciugQ}{DXtoj4WysjGbrops9mphCq}{esdata09}{SW}{8.8.2} lagging, {esdata07}{HNptjVxORhe0mU--i0km6g}{l8kuExZ-Sz-okJdIltZP7Q}{esdata07}{sw}{8.8.2} reason: lagging" logs are about 7 and 9 with no state delay, but we observe that master status is normal and there is no loss of contact.

---

<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:** [September 22, 2023, 1:23pm UTC](https://discuss.elastic.co/t/elk-loses-contact-with-the-master-every-morning-at-8am-and-the-cluster-turns-red/343621/2 "2023-09-22T13:23:13Z")

</div>

You should never run a multi-node cluster with only one master-eligible node. In order to increase resiliency [you should always look to have 3 master eligible nodes in a cluster](https://www.elastic.co/guide/en/elasticsearch/reference/8.9/high-availability-cluster-design.html).

Please share logs from the master node from around the time of the issue.

---

<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:** [October 20, 2023, 1:23pm UTC](https://discuss.elastic.co/t/elk-loses-contact-with-the-master-every-morning-at-8am-and-the-cluster-turns-red/343621/3 "2023-10-20T13:23:16Z")

</div>

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