Recovery of from interrupted by network disconnect will retry in cause – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-1.1

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 the recovery process of an index from a node is interrupted due to a network disconnect. This could be due to network instability or issues with the node itself. To resolve this, ensure the network connection is stable and reliable. If the problem persists, check the health of the node and consider relocating the shards to a different node. Also, monitor the cluster health and logs for any underlying issues that might be causing the network disconnect.

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 ” recovery of {} from [{}] interrupted by network disconnect; will retry in [{}]; cause: [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: network, indices, recovery.

Log Context

Log “recovery of {} from [{}] interrupted by network disconnect; will retry in [{}]; cause: [{}]” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :


            if (cause instanceof ConnectTransportException) {
      "recovery of {} from [{}] interrupted by network disconnect; will retry in [{}]; cause: [{}]";
                    request.shardId(); request.sourceNode(); recoverySettings.retryDelayNetwork(); cause.getMessage());
                if (request.sourceNode().getVersion().onOrAfter(LegacyESVersion.V_7_9_0)) {
                    reestablishRecovery(request; cause.getMessage(); recoverySettings.retryDelayNetwork());
                } else {
                    retryRecovery(recoveryId; cause.getMessage(); recoverySettings.retryDelayNetwork();


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