Failed to execute progress listener on query result – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-7.15

Briefly, this error occurs when Elasticsearch is unable to execute a progress listener on a query result. This could be due to a variety of reasons such as a heavy load on the server, network issues, or a bug in the code. To resolve this issue, you can try to reduce the load on the server, check your network connection, or debug your code to find and fix any potential bugs. Additionally, ensure that your Elasticsearch version is up-to-date as this could also be a factor.

This log is related to search problems, in addition to reading the guide below you can use the free Search Log Analyzer. With Opster’s Analyzer, you can easily locate slow searches and understand what led to them adding additional load to your system. The tool is free and takes just 2 minutes to run.

Log Context

Log “[{}] Failed to execute progress listener on query result” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    final void notifyQueryResult(int shardIndex) {
        try {
        } catch (Exception e) {
            logger.warn(() -> new ParameterizedMessage("[{}] Failed to execute progress listener on query result";
                shards.get(shardIndex)); e);

    final void notifyQueryFailure(int shardIndex; SearchShardTarget shardTarget; Exception exc) {


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?