Coordinating node underused
Search traffic on one or more coordinating nodes stays well below what you would expect for dedicated coordinators. Clients might be hitting data nodes directly, leaving coordinators idle and adding coordination work on data tiers.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Cluster |
| Domains | performance, resource-utilization |
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 search completed count on a coordinating node | Integer | 1000 |
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.
Completed search count is 12 on coordinating node es-data-01, below the configured minimum of 1000.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Check request routing
Condition: Always shown for this insight.
Verify applications send requests to coordinating nodes, not directly to data nodes.
Coordinating nodes distribute search and indexing requests across data nodes. When client applications connect directly to data nodes instead of dedicated coordinators, coordinating-only nodes see little traffic. That adds coordination work to data tiers and can leave dedicated coordinators underused.