---
title: Data node disconnected
description: Describes what AutoOps detects and surfaces with the Data node disconnected insight: A data node is no longer connected to the cluster.
url: https://www.elastic.co/docs/reference/autoops-insights/elasticsearch/data_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
---

# Data node disconnected
A data node is no longer connected to the cluster. Remaining nodes must handle its indexing, search, and shard work, which can slow operations and reduce availability.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://www.elastic.co/docs/reference/autoops-insights/elasticsearch).
</note>


## Insight details


| Field     | Value                     |
|-----------|---------------------------|
| Component | Elasticsearch             |
| Severity  | High                      |
| Scope     | Cluster                   |
| Domains   | 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-edge.elastic.dev/docs/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 data node has disconnected: es-data-01


#### What was detected

Disconnected node: `es-data-01` and `es-data-02`
Before the node disconnected, related conditions were observed:
-

#### 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

Data nodes hold primary and replica shards. When a data node disconnects unexpectedly, shards on that node become unavailable until replicas are promoted or reassigned. Remaining data nodes take on indexing and search work from the lost shards, which can slow operations and reduce availability.
The cluster also spends resources recovering and relocating shards. Unplanned disconnects often point to host failure, disk or memory pressure, or network problems. If multiple nodes fail in succession, cluster health can degrade quickly.

## Guide

[Delaying allocation when a node leaves](https://docs-edge.elastic.dev/docs/deploy-manage/distributed-architecture/shard-allocation-relocation-recovery/delaying-allocation-when-node-leaves)