Wipe upgraded directories – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch attempts to upgrade an index but fails to clean up the old index files. This could be due to insufficient permissions, disk space issues, or a problem with the upgrade process itself. To resolve this issue, you can manually delete the old index files, ensure that Elasticsearch has the necessary permissions to modify the directories, or check the disk space and free up space if necessary. Additionally, you can also try re-running the upgrade process after addressing these issues.

This guide will help you check for common problems that cause the log ” {} wipe upgraded directories ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: upgrade.

Log Context

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

         }


        upgradeFiles(shard; targetPath; targetPath.resolveTranslog(); ShardPath.TRANSLOG_FOLDER_NAME; paths);

        logger.info("{} wipe upgraded directories"; shard);
        for (Path path : paths) {
            if (path.equals(targetPath.getShardStatePath()) == false) {
                logger.info("{} wipe shard directories: [{}]"; shard; path);
                IOUtils.rm(path);
            }




 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?