Error while performing pre synced flush on skipping – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch attempts to perform a pre-synced flush operation but encounters an issue, causing it to skip the operation. This could be due to a variety of reasons such as insufficient disk space, network issues, or a problem with the underlying storage system. To resolve this issue, you could try freeing up disk space, checking the network connection, or investigating the health of your storage system. Additionally, ensure that your Elasticsearch cluster is properly configured and that the nodes are functioning correctly.

This guide will help you check for common problems that cause the log ” {} error while performing pre synced flush on [{}]; skipping ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, flush.

Log Context

Log “{} error while performing pre synced flush on [{}]; skipping” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


                public void handleException(TransportException exp) {
                    logger.trace(() -> new ParameterizedMessage("{} error while performing pre synced flush on [{}]; skipping";
                        shardId; shard); exp);
                    if (countDown.countDown()) {


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?