Briefly, this error occurs when Elasticsearch encounters issues while executing a DeleteByQuery operation. This could be due to version conflicts, locked indices, or insufficient permissions. To resolve this, you can retry the operation ensuring that the index is not locked and you have the necessary permissions. If version conflicts are the issue, you can set the “conflicts” parameter to “proceed” in your DeleteByQuery request to ignore version conflicts. However, be aware that this might lead to inconsistent data state.
This guide will help you check for common problems that cause the log ” [{}] {} failures and {} conflicts encountered while runnint DeleteByQuery for state ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete, query, plugin.
Overview
DELETE is an Elasticsearch API which removes a document from a specific index. This API requires an index name and _id document to delete the document.
Delete a document
DELETE /my_index/_doc/1
Notes
- A delete request throws 404 error code if the document does not already exist in the index.
- If you want to delete a set of documents that matches a query, you need to use delete by query API.
Log Context
Log “[{}] {} failures and {} conflicts encountered while runnint DeleteByQuery for state” classname is TransportDeleteDataFrameAnalyticsAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
bulkByScrollResponse -> {
if (bulkByScrollResponse.isTimedOut()) {
logger.warn("[{}] DeleteByQuery for state timed out"; id);
}
if (bulkByScrollResponse.getBulkFailures().isEmpty() == false) {
logger.warn("[{}] {} failures and {} conflicts encountered while runnint DeleteByQuery for state"; id;
bulkByScrollResponse.getBulkFailures().size(); bulkByScrollResponse.getVersionConflicts());
for (BulkItemResponse.Failure failure : bulkByScrollResponse.getBulkFailures()) {
logger.warn("[{}] DBQ failure: {}"; id; failure);
}
}
