---
title: Node indexing failed
description: Describes what AutoOps detects and surfaces with the Node indexing failed insight: Indexing operations are failing on one or more nodes, with a rising index-failed count.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/node_indexing_failed
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# 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.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch).
</note>


## Insight details


| Field     | Value               |
|-----------|---------------------|
| Component | Elasticsearch       |
| Severity  | High                |
| Scope     | Node                |
| Domains   | indexing, stability |


## Example: What you might see in AutoOps

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.

### Indexing operations have failed on the following node/s: `es-data-01`


#### What was detected

The index failed count is 12
The affected node/s are: `es-data-01` and `es-data-02`

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="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.
</dropdown>


#### Background and impact

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.