Thanks for the quick response,
Sure, I will open a issue in Github, as a new feature request and will also try to push it through our supported subscriptions.
The cluster reroute API workaround is exactly what we are using in some clusters (moving replicas and a primaries in the same reroute transaction, to a node with less primaries). But we have found 2 main drawbacks that makes this solution insufficient:
- Its a resource heavy operation, as shard data has to be moved arround.
- We need to have spare node that won't host any shard from the affected index (we cannot swap a replica and a primary between 2 nodes without using an intermediate node).