Dedicated Coordinating Nodes
Search and indexing traffic might be concentrated on nodes that also hold data shards. In larger clusters, dedicated coordinating nodes route queries to the right data nodes and spread load more evenly.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Low |
| Scope | Cluster |
| Domains | performance, node-lifecycle |
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 |
|---|---|---|
| Minimum data nodes count to introduce dedicated coordinating nodes | Integer | 5 |
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.
No description available.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Add dedicated coordinating nodes
Condition: Always shown for this insight.
Add two or three coordinating-only nodes and route searches and indexing through them to offload data nodes.
Impact: Load will be distributed unevenly across the cluster. Dedicated coordinating nodes relay search and indexing queries to the appropriate data nodes, which balances the load across the cluster. In large clusters it is recommended to add coordinating nodes to optimize the load distribution across the cluster.