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. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

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






 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content