Details
-
Improvement
-
Resolution: Fixed
-
Critical
-
7.6.2
-
0
Description
This ticket is setup to explore how FTS can exert greater control to pick a rebalance orchestrator. Currently, we do not favour any node over the other(among the nodes that will remain in the cluster after the rebalance).
This can lead to a number of issues such as incorrect partition count such as when a neo node was picked as orchestrator when upgrading from Neo -> Trinity. As we make fixes to the planner/rebalance codepaths, we should ensure that those fixes are picked up during the upgrade process of the first node being upgraded, especially when upgrading from say, 6.6.x(no longer supported and therefore will not have fixes for bugs discovered later) to 7.6.x(quite a few improvement in the planner/rebalance paths).
GSI does something similar, which can be used as a reference - https://issues.couchbase.com/browse/MB-56700.