Delaying initial state recovery for . – How to solve related issues

Average Read Time

2 Mins

Delaying initial state recovery for . – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

     private void performStateRecovery(boolean enforceRecoverAfterTime; String reason) {
        final Gateway.GatewayStateRecoveredListener recoveryListener = new GatewayRecoveryListener();

        if (enforceRecoverAfterTime && recoverAfterTime != null) {
            if (scheduledRecovery.compareAndSet(false; true)) {
                logger.info("delaying initial state recovery for [{}]. {}"; recoverAfterTime; reason);
                threadPool.schedule(() -> {
                    if (recovered.compareAndSet(false; true)) {
                        logger.info("recover_after_time [{}] elapsed. performing state recovery..."; recoverAfterTime);
                        gateway.performStateRecovery(recoveryListener);
                    }




 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content