Delaying allocation for unassigned shards; next check in – How to solve related issues

Average Read Time

2 Mins

Delaying allocation for unassigned shards; next check in – 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 ” Delaying allocation for unassigned shards; next check in ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: allocation, cluster and routing.

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



 

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

Analyze your cluster

Skip to content