Log shard state info found but indexUUID didnt match expected actual – How To Solve Related Issues

Log shard state info found but indexUUID didnt match expected actual – 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 “shard state info found but indexUUID didnt match expected actual” it’s important to understand a few problems related to Elasticsearch concepts index, shards. See bellow important tips and explanations on these concepts

Log Context

Log”{} shard state info found but indexUUID didn’t match expected [{}] actual [{}]” classname is TransportNodesListGatewayStartedShards.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 }
                // old shard metadata doesn't have the actual index UUID so we need to check if the actual uuid in the metadata
                // is equal to IndexMetaData.INDEX_UUID_NA_VALUE otherwise this shard doesn't belong to the requested index.
                if (indexUUID.equals(shardStateMetaData.indexUUID) == false
                        && IndexMetaData.INDEX_UUID_NA_VALUE.equals(shardStateMetaData.indexUUID) == false) {
                    logger.warn("{} shard state info found but indexUUID didn't match expected [{}] actual [{}]"; shardId; indexUUID; shardStateMetaData.indexUUID);
                } else {
                    logger.debug("{} shard state info found: [{}]"; shardId; shardStateMetaData);
                    return new NodeGatewayStartedShards(clusterService.localNode(); shardStateMetaData.version);
                }
            }




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 Index Shard Got Corrupted  

Github Issue Number 8707  

 

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