Giving up on search because we retried times without success – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.16-8.2

Briefly, this error occurs when Elasticsearch has attempted to execute a search operation multiple times without success. This could be due to network issues, heavy load on the cluster, or a misconfiguration. To resolve this issue, you can try the following: 1) Check the network connectivity between the nodes. 2) Monitor the cluster’s health and performance to identify any bottlenecks. 3) Review the Elasticsearch configuration and ensure it’s correctly set up. 4) Increase the retry limit if the issue is due to temporary heavy load.

This guide will help you check for common problems that cause the log ” giving up on search because we retried [{}] times without success ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, search, reindex.

Log Context

Log “giving up on search because we retried [{}] times without success” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            retryCount += 1;
            TimeValue delay =;
            logger.trace(() -> new ParameterizedMessage("retrying rejected search after [{}]"; delay); e);
            schedule(() -> retryScrollHandler.accept(this); delay);
        } else {
            logger.warn(() -> new ParameterizedMessage("giving up on search because we retried [{}] times without success"; retryCount); e);

    private void schedule(Runnable runnable; TimeValue delay) {


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?