Recovery_after_time elapsed. performing state recovery – How to solve related issues

Opster Team

Feb-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 ” Recovery_after_time elapsed. performing state recovery ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: bootstrap.

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 “recovery_after_time [{}] elapsed. performing state recovery…” classname is GatewayService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 logger.info("delaying initial state recovery for [{}]. {}"; recoverAfterTime; reason);
                threadPool.schedule(recoverAfterTime; ThreadPool.Names.GENERIC; new Runnable() {
                    
Override
                    public void run() {
                        if (recovered.compareAndSet(false; true)) {
                            logger.info("recovery_after_time [{}] elapsed. performing state recovery..."; recoverAfterTime);
                            gateway.performStateRecovery(recoveryListener);
                        }
                    }
                });
            }



 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content