Loading

Coordinating Node Disconnected

A coordinating node left the cluster without a planned removal. Clients that targeted that host will see connection or query failures until they fail over elsewhere.

Note

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.

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

-

Note

AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.

Impact: Disconnected coordinating nodes can impact the cluster's general availability, as clients accessing the cluster via coordinating nodes will receive errors. Nodes can disconnect from a cluster for a number of possible reasons. It’s important to consider that unplanned node disconnection is often a symptom of some underlying problem which must be investigated and solved. When a node disconnects it causes cluster instability because of the strain on the other nodes that need to take on all the activity that was previously shared. Additionally, the cluster needs to dedicate resources to regenerating the replica shards that have been lost from the cluster. In extreme cases this can cause a domino effect bringing down other nodes.