Failed to remove shard after failed creation – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.3-1.3

Briefly, this error occurs when Elasticsearch attempts to delete a shard that was not successfully created. This could be due to insufficient disk space, network issues, or incorrect configurations. To resolve this, you can first check the disk space and network connectivity. If these are fine, review your shard allocation settings and ensure they are correctly configured. Also, check the Elasticsearch logs for more detailed error messages that can help identify the root cause. If the issue persists, you may need to manually delete the problematic shard.

This guide will help you check for common problems that cause the log ” [{}][{}] failed to remove shard after failed creation ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, indices and shard.

Log Context

Log “[{}][{}] failed to remove shard after failed creation” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

try {
                    indexService.removeShard(shardId; "failed to create [" + ExceptionsHelper.detailedMessage(e) + "]");
                } catch (IndexShardMissingException e1) {
                    // ignore
                } catch (Throwable e1) {
                    logger.warn("[{}][{}] failed to remove shard after failed creation"; e1; shardRouting.index();;
                failedShards.put(shardRouting.shardId(); new FailedShard(shardRouting.version()));
                if (nodes.masterNode() != null) {
                    shardStateAction.shardFailed(shardRouting; indexMetaData.getUUID(); "Failed to create shard; message [" + detailedMessage(e) + "]";


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?