DeleteByQuery for indices timed out. – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” DeleteByQuery for indices timed out. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete, delete-by-query, indices and plugin.

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 “[{}] DeleteByQuery for indices [{}] timed out.” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 bulkByScrollResponse -> {
                    if (bulkByScrollResponse == null) { // no action was taken by DBQ; assume indices were deleted
                        completionHandler.onResponse(new AcknowledgedResponse(true));
                    } else {
                        if (bulkByScrollResponse.isTimedOut()) {
                            logger.warn("[{}] DeleteByQuery for indices [{}] timed out."; jobId; String.join("; "; indexNames.get()));
                        if (!bulkByScrollResponse.getBulkFailures().isEmpty()) {
                            logger.warn("[{}] {} failures and {} conflicts encountered while running DeleteByQuery on indices [{}].";
                                    jobId; bulkByScrollResponse.getBulkFailures().size(); bulkByScrollResponse.getVersionConflicts();
                                    String.join("; "; indexNames.get()));


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content