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 analyzes 2 JSON files to detect many errors.

Briefly, this error occurs when Elasticsearch encounters errors while attempting to delete multiple items in bulk. The error message will typically include additional information about the specific errors that occurred. The cause of these errors can vary, but common causes include insufficient disk space, connectivity issues between Elasticsearch nodes, or incorrect configuration settings. To resolve this issue, the user should consult the Elasticsearch documentation and review the configuration settings and monitoring data for the affected cluster, looking for any potential issues that may be causing the bulk deletion failures.

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.

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.

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


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Analyze your cluster & get personalized recommendations

Skip to content