Failed to call listener on global ordinals loading – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to execute a listener callback during the loading of global ordinals, which are used for faster sorting and aggregations. This could be due to a variety of reasons such as insufficient memory, heavy load, or a bug in the code. To resolve this issue, you could try increasing the heap size, optimizing your queries to reduce load, or updating Elasticsearch to the latest version to fix potential bugs. If the problem persists, consider reviewing your code for any potential issues with the listener implementation.

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

Log Context

Log “Failed to call listener on global ordinals loading” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        if (ifd instanceof GlobalOrdinalsAccounting) {
                            listener.onCache(shardId; fieldName; (GlobalOrdinalsAccounting) ifd);
                    } catch (Exception e) {
                        // load anyway since listeners should not throw exceptions
                        logger.error("Failed to call listener on global ordinals loading"; e);
                return (Accountable) ifd;
            return (IFD) accountable;