How To Solve Issues Related to Log – No default storage settings has been defined.

How To Solve Issues Related to Log – No default storage settings has been defined.

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 “No default storage settings has been defined.” it’s important to understand a few problems related to Elasticsearch concepts cloud-aws, cloud-azure, plugins, repository-azure, settings, storage. See bellow important tips and explanations on these concepts

Log Context

Log”no default storage settings has been defined.” classname is AzureStorageSettings.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 if (primaryStorage == null && secondaryStorage.isEmpty() == false) {
                    Map.Entry fallback = secondaryStorage.entrySet().iterator().next();
                    // We only warn if the number of secondary storage if > to 1
                    // If the user defined only one storage account; that's fine. We know it's the default one.
                    if (secondaryStorage.size() > 1) {
                        logger.warn("no default storage settings has been defined. " +
                                "Add \"default\"": true to the settings you want to activate by default. "" +

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 :

 

   

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