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

Opster Team

Feb-20, Version: 1.7-8.0



Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “shard state info found but indexUUID didnt match expected actual” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index, shards.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

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 line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now