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 run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index and shards.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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);
                }
            }




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content