syncing directory – How to solve related issues

syncing directory – 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 ” syncing directory ” 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 and Memory.

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 “{} syncing directory [{}]” classname is MultiDataPathUpgrader.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             logger.info("{} fsync files"; shard);
            for (Path moved : movedFiles) {
                logger.info("{} syncing [{}]"; shard; moved.getFileName());
                IOUtils.fsync(moved; false);
            }
            logger.info("{} syncing directory [{}]"; shard; targetDir);
            IOUtils.fsync(targetDir; true);
        }
    }






 

Run the Check-Up to get a customized report like this:

Analyze your cluster