Failed to call listener on atomic field data loading – How to solve related issues

Failed to call listener on atomic field data loading – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to call listener on atomic field data loading ” 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

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

                 for (Listener listener : k.listeners) {
                    try {
                        listener.onCache(shardId; fieldName; fieldData);
                    } catch (Exception e) {
                        // load anyway since listeners should not throw exceptions
                        logger.error("Failed to call listener on atomic field data loading"; e);
                    }
                }
                return fieldData;
            });
            return (FD) accountable;




 

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

Analyze your cluster