Coordinating node disconnected
A coordinating node left the cluster without a planned removal. Clients that targeted that host might see connection or query failures until they use other endpoints.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Cluster |
| Domains | cluster-health, node-lifecycle, stability |
You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to AutoOps event settings for details.
The default customization settings are:
| Setting | Type | Default |
|---|---|---|
| Node disconnect timeout in seconds | Integer | 300 |
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.
Disconnected node: es-data-01 and es-data-02
Before the node disconnected, related conditions were observed:
-
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
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.
Coordinating nodes route client search and bulk requests to the data nodes that hold shards. When a coordinating node leaves the cluster unexpectedly, clients that target that host see connection or query failures until they use other endpoints.
Unplanned disconnects are often a symptom of host failure, resource exhaustion, or network problems on the node or path. Remaining coordinators absorb extra client traffic, which can increase latency if capacity is tight.
If disconnects repeat or cluster health degrades, investigate the root cause on the affected node and its network path.