Queue processor found no items – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.8-8.9

Briefly, this error occurs when Elasticsearch tries to process items from a queue, but the queue is empty. This could be due to a lack of data being sent to Elasticsearch, or a problem with the data ingestion process. To resolve this issue, you can check if your data source is sending data correctly. If it is, then check your ingestion pipeline for any issues. You could also consider increasing the frequency of data ingestion or adjusting the queue size to better match your data flow.

This guide will help you check for common problems that cause the log ” queue processor found no items ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: queue, cluster.

Log Context

Log “queue processor found no items” classname is MasterService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            if (batch != null) {
                currentlyExecutingBatch = batch;
                return batch;
        logger.error("queue processor found no items");
        assert false : "queue processor found no items";
        throw new IllegalStateException("queue processor found no items");

    private void forkQueueProcessor() {


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?