Unexpected error while retrieving in flight op count – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-1.3

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch encounters an unexpected issue while trying to retrieve the count of operations currently in progress. This could be due to a network issue, a bug in the software, or a problem with the underlying storage system. To resolve this issue, you could try restarting the OpenSearch service, checking the network connectivity, or inspecting the system logs for more detailed error messages. If the problem persists, consider upgrading OpenSearch to the latest version or reaching out to the OpenSearch community for further assistance.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” {} unexpected error while retrieving in flight op count ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: indices, flush.

Log Context

Log “{} unexpected error while retrieving in flight op count” classname is SyncedFlushService.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :


                    public void handleException(TransportException exp) {
                        logger.debug("{} unexpected error while retrieving in flight op count"; shardId);

                    public String executor() {


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?

Get expert answers on Elasticsearch/OpenSearch