Description
When a backfill pipeline starts, and if a VB experiences a rollback to 0, all backfill tasks associated with the VB is deleted, with the goal that the current pipeline task starting with seqno 0 will cover the necessary ranges.
However, the backfill pipeline can get interrupted... and when the backfill pipeline is stopped and restarted, the task for the VB is no longer there to trigger the backfill. This can lead to missing backfill.
The correct thing to do should have a single backfill task for that VB from seqno 0 to represent the actual rollback to 0 scenario.
Attachments
Issue Links
- relates to
-
MB-50854 High ops rate is seen on the xdcr destination cluster while all the items seems to be replicated.
-
- Closed
-
| For Gerrit Dashboard: MB-50900 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 170518,6 | MB-50900: rollback test and injection framework for forcing a VB rollback | master | goxdcr | Status: MERGED | +2 | +1 |
| 170519,7 | MB-50900: Backfill pipeline rollback to 0 fix | master | goxdcr | Status: MERGED | +2 | +1 |