Bulk deletion failures for / items – 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 ” Bulk deletion failures for / items ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: bulk and indices.

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 “bulk deletion failures for [{}]/[{}] items” classname is IndicesTTLService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                 if (response.isFailed()) failedItems++;
                            if (logger.isTraceEnabled()) {
                                logger.trace("bulk deletion failures for [{}]/[{}] items; failure message: [{}]"; failedItems; bulkResponse.getItems().length; bulkResponse.buildFailureMessage());
                            } else {
                                logger.error("bulk deletion failures for [{}]/[{}] items"; failedItems; bulkResponse.getItems().length);
                        } else {
                            logger.trace("bulk deletion took " + bulkResponse.getTookInMillis() + "ms");


Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content