Log Delaying allocation for unassigned shards; next check in – How To Solve Related Issues

Log Delaying allocation for unassigned shards; next check in – How To Solve Related Issues

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “Delaying allocation for unassigned shards; next check in” it’s important to understand a few problems related to Elasticsearch concepts allocation, cluster, routing. See bellow important tips and explanations on these concepts

Log Context

Log”delaying allocation for [{}] unassigned shards; next check in [{}]” classname is RoutingService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             } else if (minDelaySetting  0 : "next delay must be non 0 as minDelaySetting is [" + minDelaySetting + "]";
                logger.info("delaying allocation for [{}] unassigned shards; next check in [{}]";
                        UnassignedInfo.getNumberOfDelayedUnassigned(event.state()); nextDelay);
                registeredNextDelayFuture = threadPool.schedule(nextDelay; ThreadPool.Names.SAME; new AbstractRunnable() {
                    
Override
                    protected void doRun() throws Exception {
                        minDelaySettingAtLastSchedulingNanos = Long.MAX_VALUE;



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 :

 

 

 

About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now