–> failed fetching frozen cache info from – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.12-8.2

Briefly, this error occurs when Elasticsearch is unable to retrieve information from the frozen cache. This could be due to issues with the cache itself, network connectivity problems, or insufficient permissions. To resolve this issue, you can try clearing the cache, checking your network connection, or ensuring that Elasticsearch has the necessary permissions to access the cache. Additionally, check if the frozen indices are correctly configured and accessible. If the problem persists, consider restarting the Elasticsearch service.

This guide will help you check for common problems that cause the log ” –> failed fetching frozen cache info from [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cache, plugin.

Log Context

Log “–> failed fetching frozen cache info from [{}]” classname is FrozenCacheInfoService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


        public void onFailure(Exception e) {
            logger.debug(new ParameterizedMessage("--> failed fetching frozen cache info from [{}]"; discoveryNode); e);
            // Failed even to execute the nodes info action; just give up

        private void retryOrRecordFailure(Exception e) {


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?