Log Recover-after-time elapsed. performing state recovery. – How To Solve Related Issues



Log Recover-after-time elapsed. performing state recovery. – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you read this guide, we recommend you run the Elasticsearch Error Check-Up which detects issues in ES that cause log errors. It’s a free tool that requires no installation and takes 2 minutes to complete.

This guide will help you check for common problems that cause the log ” Recover-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: recovery.

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. Among the dozens of checks included are: shards sizes, thread pools, management queue size, search errors, circuit breakers and many more (join over 700 users who use this free tool).

Log Context

Log “recover_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("recover_after_time [{}] elapsed. performing state recovery..."; recoverAfterTime);
                            gateway.performStateRecovery(recoveryListener);
                        }
                    }
                });
            }





Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 ElasticSearch: Unassigned Shards, how to fix? -views 203.11 K ,score 152

2 ElasticSearch: Unassigned Shards, how to fix? -views 203.11 K,score 152






Optimize Elasticsearch Performance

Try The Tool