Failed to close persistent cache index – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.11-8.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 Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is unable to close a persistent cache index. This could be due to a variety of reasons such as insufficient disk space, incorrect permissions, or a system failure. To resolve this issue, you can try freeing up disk space, checking and correcting file permissions, or restarting the Elasticsearch service. If the problem persists, consider clearing the cache or reindexing. Always ensure to backup your data before performing these operations to prevent data loss.

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 ” failed to close persistent cache index ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index, persistent, cache.

Log Context

Log “failed to close persistent cache index” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            } catch (IOException e) {
                try {
                } catch (Exception e2) {
                    logger.warn("failed to close persistent cache index"; e2);
                throw new UncheckedIOException("Failed to load persistent cache"; e);
            } finally {


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?