Rollup stopped before completion – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.11-7.11

Briefly, this error occurs when the rollup job in Elasticsearch, which is used to summarize and store historical data, is interrupted before it finishes. This could be due to a variety of reasons such as insufficient resources, network issues, or configuration errors. To resolve this issue, you can try restarting the rollup job, ensuring that there are sufficient resources available, checking the network connectivity, or reviewing the job configuration for any errors. Additionally, check the Elasticsearch logs for any specific error messages that may provide more insight into the problem.

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

Log Context

Log “rollup stopped before completion” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  @Override
 protected void onStop() {
 completionListener.onFailure(new ElasticsearchException("rollup stopped before completion"));
 }  @Override
 protected void onAbort() {
 completionListener.onFailure(new ElasticsearchException("rollup stopped before completion"));


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?