Failed to write shard state – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch is unable to write the state of a shard, often due to issues with disk space, permissions, or network connectivity. To resolve this, you can check if there’s enough disk space and if the Elasticsearch process has write permissions. If it’s a network issue, ensure that the nodes are properly connected. Also, check the health of your shards and consider relocating them if necessary. Lastly, ensure your Elasticsearch version is up-to-date as this could be a bug fixed in later versions.

This guide will help you check for common problems that cause the log ” failed to write shard state ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index and shard.

Log Context

Log “failed to write shard state” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 final ShardStateMetaData newShardStateMetadata = new ShardStateMetaData(newRouting.version(); newRouting.primary();
                logger.trace("{} writing shard state; reason [{}]"; shardId; writeReason);
                ShardStateMetaData.FORMAT.write(newShardStateMetadata; newShardStateMetadata.version; shardPath().getShardStatePath());
            } catch (IOException e) { // this is how we used to handle it.... :(
                logger.warn("failed to write shard state"; e);
                // we failed to write the shard state; we will try and write
                // it next time...


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?