Details
Description
Build: 7.6.0-1704
Steps:
- 2 node KV cluster (172.23.108.67 and 172.23.108.68)
- Create "default" bucket with replica=3 (Timestamp:: 6:33:26 AM 30 Oct, 2023)
- Eject 172.23.108.68 and start and stop the rebalance manually (Operation ID: 450967c2bd031e0edc6c96a6c0dfc23b , Timestamp:: 6:34:39 AM 30 Oct, 2023)
- 'pools/default' reports the buckets needs rebalance (Expected)
- Add another bucket "b1" and restart the eject node rebalance and stop again (Reb ID: 37b6b86b69fc80e64c29dc6e372855ad , Timestamp 6:35:43 AM 30 Oct, 2023)
- 'pools/default' reports both the buckets need rebalance
- Now add two nodes 172.23.108.69 and 172.23.108.70 with all services expect KV
- Start and stop the rebalance again (Reb Id: 77620047265f019ab17dce992120e81b, Timestamp 6:40:08 AM 30 Oct, 2023)
Observation:
After this, bucket rebalance required reason was gone and left only with service realance requried
"servicesNeedRebalance": [
|
"Service n1ql needs rebalance.",
|
"Service index needs rebalance.",
|
"Service fts needs rebalance.",
|
"Service cbas needs rebalance.",
|
"Service eventing needs rebalance.",
|
"Service backup needs rebalance."
|
],
|
Expected Behavior:
Both and service rebalance required should be preserved in the rebalance requirement reason
Attachments
Issue Links
- relates to
-
MB-56412 Provide reason for needing rebalance
- Closed