Default storage settings has already been defined. You can not define it to – 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 ” Default storage settings has already been defined. You can not define it to ” 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 “default storage settings has already been defined. You can not define it to [{}]” classname is AzureStorageSettings.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                         boolean activeByDefault = activeStr == null ? false : Boolean.parseBoolean(activeStr);
                        if (activeByDefault) {
                            if (primaryStorage == null) {
                                primaryStorage = current;
                            } else {
                                logger.warn("default storage settings has already been defined. You can not define it to [{}]"; storage.getKey());
                                secondaryStorage.put(storage.getKey(); current);
                            }
                        } else {
                            secondaryStorage.put(storage.getKey(); current);
                        }




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content