Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.0-beta
-
Security Level: Public
-
None
Description
There is a boundary case that caused data loss if the first checkpoint for a new active vbucket starts with id 1.
For example,
1. Node A started and has the active vb 0 with the open checkpoint 1
2 Load some items into the open checkpoint 1
3. Restart A and then A will have the open checkpoint 1 after warmup, which is empty.
4. Node B is newly joined and has the replica vb0 with the open checkpoint 1
5. Replication from A to B for vb0 doesn't schedule backfill because we thought that both node A and B have the synchronized open checkpoint for vb0.
Attachments
For Gerrit Dashboard: MB-5711 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
17688,3 | MB-5711 New active vbucket starts with the open checkpoint id > 1 | master | ep-engine | Status: MERGED | +2 | +1 |