Reducing requested field data cache size of to the maximum allowed size of – How to solve related issues

Average Read Time

2 Mins

Reducing requested field data cache size of to the maximum allowed size of – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Reducing requested field data cache size of to the maximum allowed size of ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cache, fielddata and indices.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

{{mpg_logstarted}}

Log “reducing requested field data cache size of [{}] to the maximum allowed size of [{}]” classname is IndicesFieldDataCache.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         super(settings);
        this.indicesFieldDataCacheListener = indicesFieldDataCacheListener;
        String size = componentSettings.get("size"; "-1");
        long sizeInBytes = componentSettings.getAsMemory("size"; "-1").bytes();
        if (sizeInBytes > ByteSizeValue.MAX_GUAVA_CACHE_SIZE.bytes()) {
            logger.warn("reducing requested field data cache size of [{}] to the maximum allowed size of [{}]"; new ByteSizeValue(sizeInBytes);
                    ByteSizeValue.MAX_GUAVA_CACHE_SIZE);
            sizeInBytes = ByteSizeValue.MAX_GUAVA_CACHE_SIZE.bytes();
            size = ByteSizeValue.MAX_GUAVA_CACHE_SIZE.toString();
        }
        final TimeValue expire = componentSettings.getAsTime("expire"; null);




 

Run the Check-Up to get a customized report like this:

Analyze your cluster