Node indexing failed
Indexing operations are failing on one or more nodes, with a rising index-failed count. Failures are often caused by mapping or request syntax problems, but can also reflect resource pressure on the node.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | High |
| Scope | Node |
| Domains | indexing, stability |
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 index failed count is 12
The affected node/s are: es-data-01 and es-data-02
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Check your client application logs
Condition: Always shown for this insight.
Check logs from indexing clients (Filebeat, Logstash, or custom scripts) to find why documents are failing to index.
Impact: The index failed count refers to the number of indexing operations that have been rejected, typically due to mapping or syntax related issues. If the index failed count is high and continues to grow, it might lead to data loss as requests will be rejected. This can also affect the quality of searches in your system.