Coordinating node not utilized
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.
No description available.
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.
The search request count is 12. There is a possibility that this coordinating node is not being utilized properly, which might affect the overall search performance. The job of a coordinating node is to load balance indexing and search queries across the data nodes. A low search requests count indicates that the client applications are sending only a low proportion of their search requests to the coordinating node. If you decide to use coordinating nodes, then your client applications should send all search requests to the coordinating node(s), load balancing across them if there is more than one coordinating node in the cluster.