ISM with 'min_size' and noisy neighbours

@jathin12 ,
I have over 1k tenants (and growing), therefore a separate index per tenant approach is not suitable for my use case. I’ve already started with that and then migrated to current approach of single index with multiple shards with routing.

The other approach of randomly distributed docs over the shards also doesn’t seem optimal. I fear it will hurt performance badly since every search will have to be performed over all shards rather than a single one.

In most cases, shards are more or less balanced. There are only some extreme cases when there is a noisy tenant.
Is there any other option? Do you think a ‘min_shard_size’ policy can be beneficial to this case and maybe to other people?

Thanks.