Failed to write indexing buffer for shard shard shardId ignoring – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.3-8.9

Briefly, this error occurs when Elasticsearch is unable to write the indexing buffer for a specific shard. This could be due to insufficient disk space, high I/O operations, or a faulty shard. To resolve this issue, you can try the following: 1) Check and free up disk space if necessary. 2) Reduce the load on your Elasticsearch cluster by optimizing your queries or increasing your hardware resources. 3) If a specific shard is consistently causing problems, consider reindexing your data.

This guide will help you check for common problems that cause the log ” failed to write indexing buffer for shard [” + shard.shardId() + “]; ignoring ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, indexing, shard.

Log Context

Log “failed to write indexing buffer for shard [” + shard.shardId() + “]; ignoring” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


            public void onFailure(Exception e) {
                logger.warn(() -> "failed to write indexing buffer for shard [" + shard.shardId() + "]; ignoring"; e);

    /** force checker to run now */


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?