No indices live or rollup found during rollup search – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.2-8.9

Briefly, this error occurs when Elasticsearch tries to perform a rollup search but doesn’t find any indices, either live or rollup. This could be due to incorrect index names, deleted indices, or lack of permissions. To resolve this, ensure that the index names are correct and that they exist in your Elasticsearch cluster. Also, check if the user has the necessary permissions to access the indices. If the indices were deleted, you may need to recreate them or restore from a backup.

This guide will help you check for common problems that cause the log ” No indices (live or rollup) found during rollup search ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, search, indices.

Log Context

Log “No indices (live or rollup) found during rollup search” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // If we only have a live index left; just return it directly. We know it can't be an error already
 if (rolledResponses.isEmpty() && liveResponse != null) {
 return liveResponse;
 } else if (rolledResponses.isEmpty()) {
 throw new ResourceNotFoundException("No indices (live or rollup) found during rollup search");
 }  return doCombineResponse(liveResponse; rolledResponses; reduceContextBuilder);