Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
3.0
-
Security Level: Public
-
None
-
Untriaged
-
Unknown
-
Mar 9 - Mar 27
Description
Setup 4-node cluster with beer-sample bucket and workload running on it. Graceful failover one node, wait a few minutes, delta recover back in. The rebalance failed once due to dcp_wait_for_data_move_failed. I gathered logs and then retried the rebalance a number of times, it failed all times with the same error.
Build 1208
Logs are at:
https://s3.amazonaws.com/cb-customers/mb11980/collectinfo-2014-09-05T202245-ns_1%40ec2-54-176-254-88.us-west-1.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-customers/mb11980/collectinfo-2014-09-05T202245-ns_1%40ec2-54-176-54-69.us-west-1.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-customers/mb11980/collectinfo-2014-09-05T202245-ns_1%40ec2-54-219-84-241.us-west-1.compute.amazonaws.com.zip
https://s3.amazonaws.com/cb-customers/mb11980/collectinfo-2014-09-05T202245-ns_1%40ec2-54-219-94-38.us-west-1.compute.amazonaws.com.zip
Attachments
| For Gerrit Dashboard: MB-12137 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 41269,1 | MB-12137: Use the disk seqno if it's greater than the max persist seqno | 3.0 | ep-engine | Status: ABANDONED | -1 | 0 |
| 41289,2 | MB-12137: Don't update the current snapshot during persistence | 3.0 | ep-engine | Status: MERGED | +2 | +1 |