Setting – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

index.number_of_shards] cannot be changed after index creation. Briefly, this error occurs when there’s an attempt to change the number of shards for an existing Elasticsearch index. Elasticsearch doesn’t allow changing the number of shards after an index has been created. To resolve this issue, you can either reindex your data into a new index with the desired number of shards or use the Split Index API to increase the number of shards if you initially set the index to be resizable. However, reducing the number of shards can only be done by reindexing.

This guide will help you check for common problems that cause the log ” Setting [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Setting [” class name is OpenIdConnectRealm.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 .stream()
 .filter(Objects::nonNull)
 .collect(Collectors.toList()));
 }
 } else if (required) {
 throw new SettingsException("Setting [" + RealmSettings.getFullSettingKey(realmConfig; setting.getClaim())
 + "] is required");
 } else if (realmConfig.hasSetting(setting.getPattern())) {
 throw new SettingsException("Setting [" + RealmSettings.getFullSettingKey(realmConfig; setting.getPattern())
 + "] cannot be set unless [" + RealmSettings.getFullSettingKey(realmConfig; setting.getClaim())
 + "] is also set");

 

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?