Briefly, this error occurs when Elasticsearch encounters issues while executing a DeleteByQuery operation for a specific state. This could be due to version conflicts, locked indices, or insufficient permissions. To resolve this, you can try the following: 1) Ensure you have the necessary permissions to perform the operation. 2) Check if the indices are locked and unlock them if necessary. 3) If version conflicts are the issue, consider using the “conflicts” parameter in your DeleteByQuery request to manage how conflicts are handled.
This guide will help you check for common problems that cause the log ” [{}] {} failures and {} conflicts encountered while running DeleteByQuery for state ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete, plugin, query.
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 running DeleteByQuery for state” classname is DataFrameAnalyticsDeleter.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 running DeleteByQuery for state"; id;
bulkByScrollResponse.getBulkFailures().size(); bulkByScrollResponse.getVersionConflicts());
for (BulkItemResponse.Failure failure : bulkByScrollResponse.getBulkFailures()) {
logger.warn("[{}] DBQ failure: {}"; id; failure);
}
}
