How To Solve Issues Related to Log – Value for setting

Get an Elasticsearch Check-Up

Check if your ES issues are caused from misconfigured settings
(Free 2 min process)

Check-Up

Last update: Jan-20

Elasticsearch Error Guide In Page Navigation (click to jump) :

Troubleshooting Background – start here to get the full picture       
Related Issues – selected resources on related issues  
Log Context – usefull for experts
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check Your Elasticsearch Settings for Painfull Mistakes 


Troubleshooting background

To troubleshoot Elasticsearch log “Value for setting” it’s important to know common problems related to Elasticsearch concepts: discovery, elect, master. See below-detailed explanations complete with common problems, examples and useful tips.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

Whats Means Cloudoc1 Value For Sett
discuss.elastic.co/t/whats-means-cloudoc1-value-for-setting-discovery-zen-minimum-master-nodes-is-too-low/155323

 

Github Issue Number 18645
github.com/elastic/elasticsearch/issues/18645

 


Log Context

Log ”Value for setting” classname is ElectMasterService.java
We have extracted the following from Elasticsearch source code to get an in-depth context :

     }

    public void logMinimumMasterNodesWarningIfNecessary(ClusterState oldState; ClusterState newState) {
        // check if min_master_nodes setting is too low and log warning
        if (hasTooManyMasterNodes(oldState.nodes()) == false && hasTooManyMasterNodes(newState.nodes())) {
            logger.warn("value for setting \"{}\"" is too low. This can result in data loss! Please set it to at least a quorum of master-"" +
                    ""eligible nodes (current value: [{}]; total number of master-eligible nodes used for publishing in this round: [{}])"";
                ElectMasterService.DISCOVERY_ZEN_MINIMUM_MASTER_NODES_SETTING.getKey(); minimumMasterNodes();
                newState.getNodes().getMasterNodes().size());
        }
    }




"

About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues

We are constantly updating our analysis of Elasticsearch logs, errors, and exceptions. Sharing best practices and providing troubleshooting guides.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?