Warm Nodes Indexing
Significant indexing activity is running on nodes outside the hot tier. Warm and cold tiers are optimized for retention cost, not ingest throughput.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Cluster |
| Domains | performance, indexing, index-management |
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 affected node/s are: - logs-prod-000045: indexing rate - 1,200 docs/s Indices with the highest indexing rate: logs-prod-000045
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Review data tier architecture
Condition: Always shown for this insight.
Review whether your hot, warm, cold, and frozen tiers match data age, query patterns, and cost goals.
Review templates and ILM
Condition: Always shown for this insight.
Review index templates and ILM policies so new write indices stay on the hot tier until rollover is appropriate. Premature moves to colder tiers usually mean the ILM policy is misconfigured.
Move shard to hot tier
Condition: Shown when index on non-hot tier can be moved to hot nodes that can host the index shards.
Move shard 0 of index logs-prod-000045 from warm node es-data-01 to hot node es-data-02 using the action below.
POST _cluster/reroute
{
"commands": [
{
"move": {
"index": "logs-prod-000045",
"shard": 0,
"from_node": "es-data-01",
"to_node": "es-data-02"
}
}
]
}
Requires the manage cluster privilege. Requires Elasticsearch 8.0.0 or later. This action changes cluster or index configuration.
We detected that you have indexing operations outside of your hot tier and it is not recommended to do so. There might be several reasons to that, for instance:
- A wrongly configured ILM policy moving indices still being written to outside of the hot tier too prematurely
- Bad cluster or shard allocation filtering rules forcing the index to be located on the wrong tier