Bulk request has been cancelled. – 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 analyzes 2 JSON files to detect many errors.

Briefly, this error occurs when a bulk request that was being executed by Elasticsearch was cancelled before it could be completed. This can happen due to a timeout, a server shutdown, or an error in the request. To resolve the issue, identify the cause of the cancellation and address it. For example, you may need to increase the timeout or optimize the request to reduce the load on the Elasticsearch server.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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: bulk, handler and request.


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) {
                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 {




 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content