---
title: Node indexing failures
description: Describes what AutoOps detects and surfaces with the Node indexing failures 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_failures
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 failures
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 nodes: es-data-01


#### What was detected

The index failed count is 12.
Affected nodes: `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

When Elasticsearch rejects indexing operations on a node, documents do not reach the index. Common causes include mapping conflicts, malformed JSON, strict dynamic mapping, and resource pressure on the node.
If failures continue, data can lag behind client expectations and search results can miss recent documents.

## Guide

[Tune for indexing speed](https://docs-v3-preview.elastic.dev/elastic/docs-content/tree/main/deploy-manage/production-guidance/optimize-performance/indexing-speed)