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

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. 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: 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 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 “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 Check-Up to get a customized report like this:

Analyze your cluster