How To Solve Issues Related to Log – upgrading from to

How To Solve Issues Related to Log – upgrading from to

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “upgrading from to” it’s important to understand a few problems related to Elasticsearch concepts Index, Memory. See bellow important tips and explanations on these concepts

Log Context

Log”{} upgrading [{}] from [{}] to [{}]” classname is MultiDataPathUpgrader.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         List movedFiles = new ArrayList<>();
        for (Path path : paths) {
            if (path.equals(targetPath.getDataPath()) == false) {
                final Path sourceDir = path.resolve(folderName);
                if (Files.exists(sourceDir)) {
                    logger.info("{} upgrading [{}] from [{}] to [{}]"; shard; folderName; sourceDir; targetDir);
                    try (DirectoryStream stream = Files.newDirectoryStream(sourceDir)) {
                        Files.createDirectories(targetDir);
                        for (Path file : stream) {
                            if (IndexWriter.WRITE_LOCK_NAME.equals(file.getFileName().toString()) || Files.isDirectory(file)) {
                                continue; // skip write.lock




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 Solved Error Request To Elasticsear  

Help After Upgrading To Elasticsear  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now