-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
S
It seems that the setting $.es.settings.number_of_shards is not being used at all in the codebase. This was due to an unintended change in OPT-7348. So we have to re-add the usage to the code base
Testing notes
Changing the number of shards in the config ($.es.settings.number_of_shards) should be reflected to the database.
NOTE: this property only applies the first time Optimize is started and the schema/mapping is deployed on Elasticsearch. If you want to take this property to take effect again, you need to delete all indexes (with it all data) and restart Optimize. This configuration will also only be applied to the current write instance indices. Archive indices will have a single shard regardless
