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

Opster Team

Aug-23, Version: 6.8-8.2

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) Monitor and optimize your I/O operations to prevent overloading. 3) Try relocating the shard to another node. 4) If the shard is corrupt, consider reindexing your data.

This guide will help you check for common problems that cause the log ” failed to write indexing buffer for shard [{}]; 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 [{}]; 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(() -> new ParameterizedMessage("failed to write indexing buffer for shard [{}]; ignoring"; shard.shardId()); 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?