2 buckets (~10 M items)
10 index building in progress
3 compaction on views in progress
The CPU usage here was about 80% on the orchestrator.
It took about 10 mins for stop rebalance to take effect, from user perpective, it seems as though stop rebalance did not work.
We could can log in UI, saying that stop rebalance is in progress, since, I believe stop rebalance is asyn call.
Attaching the cbcollect_logs from the orchestrator.