Why doesn't the primary shard switched away from the node being decommissioned?
When I use cluster.routing.allocation.exclude._name to exclude a node from participating the cluster (and be removed eventually), I noticed that I still have primary shard locating in the node preparing to be decommissioned. That shard is marked as "relocating".
Wouldn't it make sense to make the replica shard in different node the primary in such scenario?
That way all the writes will go to one of the other participating nodes instead of the one being excluded?
I'm running version 7.3.1.
I'm seeing longer rebalancing time compare to before, and not sure if this could be the culprit.