Details
-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
6.5.0
-
6.5.0-3853
-
Triaged
-
Centos 64-bit
-
No
-
KV-Engine MH Beta part 2
Description
Seeing rebalance getting stuck at 45.8984375% during replica update case.
Scenario:
- 4 node cluster, couchbase bucket (replica=0)
- Loaded 2 docs with durability=MAJORITY
- Updated replica from 0 -> 3 in incremental manner
Observation:
Rebalance struck when updating replica=3 from replica=2 and rebalance.
cbcollect_info:
https://cb-jira.s3.us-east-2.amazonaws.com/logs/MB35258_on_replica_update/collectinfo-2019-07-24T102756-ns_1%4010.112.191.101.zip
https://cb-jira.s3.us-east-2.amazonaws.com/logs/MB35258_on_replica_update/collectinfo-2019-07-24T102756-ns_1%4010.112.191.102.zip
https://cb-jira.s3.us-east-2.amazonaws.com/logs/MB35258_on_replica_update/collectinfo-2019-07-24T102756-ns_1%4010.112.191.103.zip
https://cb-jira.s3.us-east-2.amazonaws.com/logs/MB35258_on_replica_update/collectinfo-2019-07-24T102756-ns_1%4010.112.191.104.zip
Rebalance UI status:
Attachments
Issue Links
- duplicates
-
MB-35245 [Chain Rebalance]: Subsequent rebalance in of 2 nodes failed because Disk ckpt streamed as Memory ckpt
- Closed