Multiple default Azure data stores configured – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-6.8

Briefly, this error occurs when there are multiple Azure data stores configured as default in Elasticsearch. This can cause confusion and conflicts as Elasticsearch wouldn’t know which one to use. To resolve this issue, you can either remove the extra default data stores or specify one as the default. You can do this by updating the configuration files or using the Elasticsearch API. Make sure to restart Elasticsearch after making these changes for them to take effect.

This guide will help you check for common problems that cause the log ” Multiple default Azure data stores configured: [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: azure, repository-azure, plugins, repositories.

Log Context

Log “Multiple default Azure data stores configured: [” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 for (AzureStorageSettings setting : settings) {
 if (setting.isActiveByDefault()) {
 if (primary == null) {
 primary = setting;
 } else {
 throw new SettingsException("Multiple default Azure data stores configured: [" + primary.getName()
 + "] and [" + setting.getName() + "]");
 if (primary == null) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?