Currently, there is no way to centrally control index settings with an index template for dedicated Elasticsearch metric stores. This means every new Rally execution has a chance of applying its own, for example, datastore.number_of_shards configuration which could differ from run to run. Differing configurations are ignored for existing metrics indices, though new indices could receive undesired settings.
This proposal is in further support of composable templates, see https://github.com/elastic/rally/pull/1811. Index settings can be decoupled from the main component template and placed into a component template where they would be left untouched by subsequent Rally executions.
Currently, there is no way to centrally control index settings with an index template for dedicated Elasticsearch metric stores. This means every new Rally execution has a chance of applying its own, for example,
datastore.number_of_shardsconfiguration which could differ from run to run. Differing configurations are ignored for existing metrics indices, though new indices could receive undesired settings.This proposal is in further support of composable templates, see https://github.com/elastic/rally/pull/1811. Index settings can be decoupled from the main component template and placed into a component template where they would be left untouched by subsequent Rally executions.