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 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. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” No deletion job listeners could be found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete, listeners and plugin.

Log Context

Log “[{}] No deletion job listeners could be found” classname is
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);
            for (ActionListener listener : listeners) {
                if (error != null) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content