---
title: Master Node Disconnected
description: Describes what AutoOps detects and surfaces with the Master Node Disconnected insight: A master-eligible node has disconnected from the cluster.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/master_node_disconnected
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# Master Node Disconnected
A master-eligible node has disconnected from the cluster. Losing masters can cause coordination instability and, in extreme cases, loss of quorum that makes the cluster unavailable.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch).
</note>


## Insight details


| Field     | Value                                     |
|-----------|-------------------------------------------|
| Component | Elasticsearch                             |
| Severity  | Medium                                    |
| Scope     | Cluster                                   |
| Domains   | cluster-health, node-lifecycle, stability |


## Customization settings

You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to [AutoOps event settings](https://docs-v3-preview.elastic.dev/elastic/docs-content/tree/main/deploy-manage/monitor/autoops/ec-autoops-event-settings) for details.
The default customization settings are:

| Setting                            | Type    | Default |
|------------------------------------|---------|---------|
| Node disconnect timeout in seconds | Integer | 300     |


## Example: What you might see in AutoOps

The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.

### The following master node has disconnected: `es-data-01`


#### What was detected

The disconnected node is: `es-data-01` and `es-data-02` Before the disconnection of the nodes, the system detected the following indications:
-

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="Investigate disconnected node activity">
  **Condition**: Always shown for this insight.Review tasks, slow search logs, and indexing logs from before the disconnect to find costly requests or errors that might have caused the node to drop.
</dropdown>


#### Background and impact

The loss of master nodes can cause instability in the cluster, or in extreme cases can make the entire cluster become unavailable.
The loss of master nodes can create a situation of lack of quorum causing the cluster to become unavailable until a new master is brought into the cluster.