As I mentioned in MB-32642 different types of rebalance can take different amount of time because they may be moving different # of vBuckets.
In a 4 -> 3 rebalance out, 512 vBuckets will be moved in each bucket,
In a 3 ->2 rebalance out (which is the case here), 680 vBuckets will be moved in each bucket.
So, it is expected that the 3 ->2 will take longer.
I checked the logs. There are total 32 buckets (30 + 2 eventing buckets). Each bucket rebalance is taking ~30-40 minutes.
Rebalance was running for around 12 1/2 hours when cbcollect was issued. And, had rebalanced 22 buckets.
- We need logs from the orchestrator node (172.23.96.20) for the 3 ->2 rebalance.
- Also, need logs from 4 ->3 rebalance.
- Then we can compare the two to see where the time is spent for each, how long vBucket moves are taking and so one. This will help then determine whether 3 ->2 rebalance is taking longer primarily because it is moving 168 (=680 -512) more vBuckets or something else.
Poonam Dhavale - Can you please take a look at this?