Delaying initial state recovery for – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to perform the initial state recovery immediately due to some internal issues like high load, network issues, or node failures. This could also be due to the cluster being in a red state. To resolve this issue, you can try reducing the load on the cluster, checking the network connectivity, or ensuring that all nodes are functioning properly. If the cluster is in a red state, you need to identify and fix the underlying issues causing this state.

This guide will help you check for common problems that cause the log ” delaying initial state recovery for [{}]. {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: recovery.

Log Context

Log “delaying initial state recovery for [{}]. {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    private void performStateRecovery(final boolean enforceRecoverAfterTime; final String reason) {
        if (enforceRecoverAfterTime && recoverAfterTime != null) {
            if (scheduledRecovery.compareAndSet(false; true)) {
      "delaying initial state recovery for [{}]. {}"; recoverAfterTime; reason);
                threadPool.schedule(new AbstractRunnable() {
                    public void onFailure(Exception e) {
                        logger.warn("delayed state recovery failed"; e);


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?