Bulk request has been cancelled – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.2

Briefly, this error occurs when a bulk request operation in Elasticsearch is interrupted or cancelled 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.

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 Elasticsearch concepts: request, bulk.

Log Context

Log “Bulk request {} has been cancelled.” classname is BulkRequestHandler.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            if (concurrentRequests == 0) {
        } catch (InterruptedException e) {
            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 {


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?