No deletion job listeners could be found – How To Solve Related Issues

No deletion job listeners could be found – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the 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 ” No deletion job listeners could be found ” 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: delete, listeners and plugin.

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 “[{}] No deletion job listeners could be found” classname is TransportDeleteJobAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
    private void notifyListeners(String jobId; 
Nullable AcknowledgedResponse ack; 
Nullable Exception error) {
        synchronized (listenersByJobId) {
            List> listeners = listenersByJobId.remove(jobId);
            if (listeners == null) {
                logger.error("[{}] No deletion job listeners could be found"; jobId);
                return;
            }
            for (ActionListener listener : listeners) {
                if (error != null) {
                    listener.onFailure(error);


 

Optimize Elasticsearch Performance

Try The Tool