Dedicated coordinating nodes
Elastic Cloud Hosted lets you manage and configure one or more deployments of the versioned Elastic Stack, hosted on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Elastic Cloud Enterprise is a self-managed orchestration platform for deploying and managing the Elastic Stack at scale. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Self-managed deployments are Elastic Stack deployments managed without the assistance of an orchestrator. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
ECH
Generally available
ECK
Generally available
ECE
Generally available
Self-managed
Generally available
Your cluster has enough data nodes that dedicated coordinating nodes are recommended, and none were detected. Coordinating-only nodes route search and indexing traffic so data nodes are not also the sole entry points for client load.
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 node count to recommend 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.
Your cluster has at least as many data nodes as your configured minimum for this insight (default 5), and no dedicated coordinating-only nodes were detected.
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.
Coordinating nodes fan out search and indexing requests to the right data nodes and gather responses. In larger clusters, sending all client traffic through data nodes can create hot spots and uneven load.
Dedicated coordinating-only nodes spread that traffic and keep coordination work off data-heavy nodes. Without them, some data nodes can absorb most query and bulk load while others stay quieter.