Get from cache index timed out after 5s retrieving from blob store instead – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.1-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 takes longer than the set timeout period to retrieve data from the cache index, and instead tries to retrieve it from the blob store. This could be due to network latency, heavy load on the cluster, or a misconfigured timeout setting. To resolve this, you can increase the timeout setting, optimize your queries to reduce load, or improve your network connectivity. Additionally, ensure your blob store is properly configured and accessible to avoid fallback scenarios.

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 ” get from cache index timed out after [5s]; retrieving from blob store instead ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index, cache.

Log Context

Log “get from cache index timed out after [5s]; retrieving from blob store instead” classname is BlobStoreCacheService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        generateId(repository; snapshotId; indexId; shardId; name; range)
                    );
                    e
                );
            } else {
                logger.warn("get from cache index timed out after [5s]; retrieving from blob store instead");
            }
            return CachedBlob.CACHE_NOT_READY;
        }
    }

 

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?