Failed to call listener on field data cache unloading – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Failed to call listener on field data cache unloading ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cache, fielddata and indices.

Log Context

Log “Failed to call listener on field data cache unloading” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     key.shardId; indexCache.fieldName;
                    notification.getRemovalReason() == RemovalNotification.RemovalReason.EVICTED; value.ramBytesUsed()
            } catch (Exception e) {
                // load anyway since listeners should not throw exceptions
                logger.error("Failed to call listener on field data cache unloading"; e);

    public static class FieldDataWeigher implements ToLongBiFunction {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content