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

Opster Team

Aug-23, Version: 1.2-2.9

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 has attempted to execute a search request multiple times but has failed each time. This could be due to issues like network problems, heavy load on the cluster, or insufficient resources. To resolve this, you can increase the retry count, optimize your search queries to reduce load, or scale up your OpenSearch cluster to provide more resources. Additionally, check your network connectivity to ensure there are no interruptions.

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 ” 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 OpenSearch concepts: index, search, reindex.

Log Context

Log “giving up on search because we retried [{}] times without success” classname is
We extracted the following from OpenSearch 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?

Get expert answers on Elasticsearch/OpenSearch