# Cluster become red

**URL:** <https://discuss.elastic.co/t/cluster-become-red/217950>\
**Category:** Elasticsearch\
**Created:** [February 5, 2020, 9:58am UTC](https://discuss.elastic.co/t/cluster-become-red/217950 "2020-02-05T09:58:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ivan\_Kulynych](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ivan_kulynych/32/52451_2.png) [@Ivan\_Kulynych](https://discuss.elastic.co/u/Ivan_Kulynych)\
**Post date:** [February 5, 2020, 9:58am UTC](https://discuss.elastic.co/t/cluster-become-red/217950/1 "2020-02-05T09:58:08Z")

</div>

Hi colleagues, after migrating my Elasticsearch cluster from Docker 6.2.2 version to VMs with 6.8.5 version, my cluster periodically get RED status. In logs I see that some node left the cluster. On the node that left cluster I see only messages like "node [NlxDLTjjQMi4tWf\_2PPAVQ] is not available"  
But I don't see any network issues.  
I have 5 nodes  
xpack.security.enabled: true  
xpack.security.transport.ssl.enabled: true  
xpack.security.transport.ssl.verification\_mode: certificate

---

<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:** [March 4, 2020, 9:58am UTC](https://discuss.elastic.co/t/cluster-become-red/217950/2 "2020-03-04T09:58:23Z")

</div>

Closed on March 4, 2020, 9:58am UTC

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