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

Opster Team

Aug-23, Version: 7.6-7.15

Briefly, this error occurs when Elasticsearch fails to execute a progress listener due to a query failure. This could be due to a variety of reasons such as incorrect query syntax, insufficient resources, or network issues. To resolve this issue, you can check the query syntax for any errors, ensure that the Elasticsearch cluster has enough resources to execute the query, and verify that there are no network connectivity issues. Additionally, you can check the Elasticsearch logs for more detailed error messages that can help identify the root cause of the problem.

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 failure” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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

    final void notifyPartialReduce(List shards; TotalHits totalHits; InternalAggregations aggs; int reducePhase) {


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?