Nodes failed to run deprecation checks: – 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 ” Nodes failed to run deprecation checks: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: deprecation and plugin.

Log Context

Log “Nodes failed to run deprecation checks: {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 ActionListener.wrap(response -> {
                if (response.hasFailures()) {
                    List failedNodeIds = response.failures().stream()
                        .map(failure -> failure.nodeId() + ": " + failure.getMessage())
                    logger.warn("nodes failed to run deprecation checks: {}"; failedNodeIds);
                    for (FailedNodeException failure : response.failures()) {
                        logger.debug("node {} failed to run deprecation checks: {}"; failure.nodeId(); failure);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content