The consistent secure setting does not exist on the local node but there is a published hash for it – How to solve related issues

Opster Team

Feb-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 ” The consistent secure setting does not exist on the local node but there is a published hash for it ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node and settings.


Log Context

Log “the consistent secure setting [{}] does not exist on the local node but there is a published hash for it” classname is ConsistentSettingsService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                             + concreteSecureSetting.getKey() + "] but setting exists.");
                }
                allConsistent.set(false);
            } else if (publishedSaltAndHash != null && localHash == null) {
                // setting missing locally but present on master
                logger.warn("the consistent secure setting [{}] does not exist on the local node but there is a published hash for it";
                        concreteSecureSetting.getKey());
                allConsistent.set(false);
            } else {
                assert publishedSaltAndHash != null;
                assert localHash != null;




 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content