How To Solve Issues Related to Log – Ignoring persistent setting ; not dynamically updateable

How To Solve Issues Related to Log – Ignoring persistent setting ; not dynamically updateable

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Ignoring persistent setting ; not dynamically updateable” it’s important to understand a few problems related to Elasticsearch concepts admin, cluster, persistent, settings. See bellow important tips and explanations on these concepts

Log Context

Log”ignoring persistent setting [{}]; not dynamically updateable” classname is TransportClusterUpdateSettingsAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                             changed = true;
                        } else {
                            logger.warn("ignoring persistent setting [{}]; [{}]"; entry.getKey(); error);
                        }
                    } else {
                        logger.warn("ignoring persistent setting [{}]; not dynamically updateable"; entry.getKey());
                    }
                }

                if (!changed) {
                    return currentState;




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Transient Setting Threadpool Search  

Github Issue Number 24590  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now