still pending deletes present for shards retrying – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” still pending deletes present for shards retrying ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices and shards.

Log Context

Log “{} still pending deletes present for shards {} – retrying” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    if (remove.isEmpty() == false) {
                        logger.warn("{} still pending deletes present for shards {} - retrying"; index; remove.toString());
                        sleepTime = Math.min(maxSleepTimeMs; sleepTime * 2); // increase the sleep time gradually
                        logger.debug("{} schedule pending delete retry after {} ms"; index; sleepTime);
                } while ((System.nanoTime() - startTimeNS) 


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content