Has anyone addressed Auto-Scaling the Shards per index, currently via templates, when ECE expands the cluster's nodes ?
Today, we have 24 Data Nodes in our non-ECE based cluster.
- Via our Templates, we have set
Per index, 11 Primary and 1 Replica shards per index, (so totaling 22) and
The total_shards_per_node set to 1 in the templates, so that we don’t get a busy node w/ multiple shards on it.
This allows us to take 2 nodes offline (or to have hit the high/low water marks) without having an impact.
The ECE ‘challenge’ is to be able to increase the number of shards per index as we expand the nodes.
While we are considering how Shard Size limitations coming will help with this, we could still end up with a full node or more likely a Busy node when we have everything going to a single node.