Shard %s rollup cancelled – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.7-8.9

Briefly, this error occurs when a rollup job on a specific shard in Elasticsearch is cancelled. This could be due to a variety of reasons such as system overload, network issues, or manual interruption. To resolve this issue, you can try the following: 1) Check the system resources and ensure they are not overloaded. 2) Verify the network connectivity between the nodes. 3) If the job was manually cancelled, you can restart it. 4) Check the Elasticsearch logs for any specific issues related to the rollup job.

This guide will help you check for common problems that cause the log ” Shard %s rollup cancelled ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, shard.

Log Context

Log “Shard %s rollup cancelled” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new TaskCancelledException(format("Shard %s rollup cancelled"; indexShard.shardId()));
 }  private BulkProcessor2 createBulkProcessor() {
 final BulkProcessor2.Listener listener = new BulkProcessor2.Listener() {


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?