No default storage settings has been defined. – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” No default storage settings has been defined. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cloud-aws, cloud-azure, plugins, repository-azure and settings.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “no default storage settings has been defined.” classname is
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. "" +


Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content