Log marking unavailable shards as stale: – How To Solve Related Issues

Log marking unavailable shards as stale: – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0


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 “marking unavailable shards as stale:” it’s important to understand a few problems related to Elasticsearch concepts allocation, cluster, index, routing, shards. See bellow important tips and explanations on these concepts

Log Context

Log”{} marking unavailable shards as stale: {}” classname is IndexMetaDataUpdater.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     if (indexMetaDataBuilder == null) {
                        indexMetaDataBuilder = IndexMetaData.builder(oldIndexMetaData);
                    indexMetaDataBuilder.putInSyncAllocationIds(shardNumber; remainingInSyncAllocations);
                logger.warn("{} marking unavailable shards as stale: {}"; shardEntry.getKey(); idsToRemove);

            if (indexMetaDataBuilder != null) {
                if (metaDataBuilder == null) {
                    metaDataBuilder = MetaData.builder(oldMetaData);

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 Shard unassigned after failing to flush in elastic search

4.01 K 3

Elasticsearch 6 3 2 The Index Is Au  


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