Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.
Briefly, this error occurs when a bulk request in OpenSearch is interrupted before it can be completed. This could be due to a timeout, a system shutdown, or a manual cancellation. To resolve this issue, you can try increasing the timeout limit, ensuring the system remains operational during the request, or avoiding manual interruptions. If the problem persists, consider breaking down the bulk request into smaller parts to reduce the load on the system.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
This guide will help you check for common problems that cause the log ” Bulk request {} has been cancelled. ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: bulk, request.
Log Context
Log “Bulk request {} has been cancelled.” classname is BulkRequestHandler.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
if (concurrentRequests == 0) {
latch.await();
}
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
logger.info(() -> new ParameterizedMessage("Bulk request {} has been cancelled."; executionId); e);
listener.afterBulk(executionId; bulkRequest; e);
} catch (Exception e) {
logger.warn(() -> new ParameterizedMessage("Failed to execute bulk request {}."; executionId); e);
listener.afterBulk(executionId; bulkRequest; e);
} finally {
