Log Recovery_after_time elapsed. performing state recovery – How To Solve Related Issues


Log 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 try running the 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: bootstrap.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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);
                        }
                    }
                });
            }



 

Optimize Elasticsearch Performance

Try The Tool