Log loaded shard state – How To Solve Related Issues

Log loaded shard state – 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 that cause many errors.

This guide will help you check for common problems that cause the log ” loaded shard state ” 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: shard.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log context

Log “{} loaded shard state {}” classname is MultiDataPathUpgrader.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         logger.info("{} upgrading multi data dir to {}"; shard; targetPath.getDataPath());
        final ShardStateMetaData loaded = ShardStateMetaData.FORMAT.loadLatestState(logger; paths);
        if (loaded == null) {
            throw new IllegalStateException(shard + " no shard state found in any of: " + Arrays.toString(paths) + " please check and remove them if possible");
        logger.info("{} loaded shard state {}"; shard; loaded);

        ShardStateMetaData.FORMAT.write(loaded; loaded.version; targetPath.getShardStatePath());
        try (SimpleFSDirectory directory = new SimpleFSDirectory(targetPath.resolveIndex())) {
            try (final Lock lock = directory.obtainLock(IndexWriter.WRITE_LOCK_NAME)) {


Optimize Elasticsearch Performance

Try The Tool