Exception during periodic request cache cleanup – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-2.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch encounters an issue during its routine task of cleaning up the request cache. This could be due to a variety of reasons such as insufficient memory, corrupted cache, or a bug in the system. To resolve this issue, you could try clearing the cache manually, increasing the memory allocation for OpenSearch, or updating OpenSearch to the latest version to fix potential bugs. If the problem persists, consider checking the system logs for more detailed error information.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Exception during periodic request cache cleanup: ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: request, cache, indices.

Log Context

Log “Exception during periodic request cache cleanup:” classname is IndicesService.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :


            try {
            } catch (Exception e) {
                logger.warn("Exception during periodic request cache cleanup:"; e);
            // Reschedule itself to run again if not closed
            if (closed.get() == false) {
                threadPool.scheduleUnlessShuttingDown(interval; ThreadPool.Names.SAME; this);


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?

Get expert answers on Elasticsearch/OpenSearch