Log Failed to mark shard as failed (because of ) – How To Solve Related Issues

Log Failed to mark shard as failed (because of ) – How To Solve Related Issues

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “Failed to mark shard as failed (because of )” it’s important to understand a few problems related to Elasticsearch concepts cluster, indices, shard. See bellow important tips and explanations on these concepts

Log Context

Log”[{}][{}] failed to mark shard as failed (because of [{}])” classname is IndicesClusterStateService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         try {
            logger.warn("[{}] marking and sending shard failed due to [{}]"; failure; shardRouting.shardId(); message);
            failedShards.put(shardRouting.shardId(); new FailedShard(shardRouting.version()));
            shardStateAction.shardFailed(shardRouting; indexUUID; message; failure);
        } catch (Throwable e1) {
            logger.warn("[{}][{}] failed to mark shard as failed (because of [{}])"; e1; shardRouting.getIndex(); shardRouting.getId(); message);
        }
    }

    private class FailedEngineHandler implements Engine.FailedEngineListener {
        
Override



Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Fail To Assign Shards After Restart  

Github Issue Number 37888  

 

About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now