Details
-
Bug
-
Resolution: Fixed
-
Major
-
5.5.5, 6.5.0
-
Security Level: Public
-
Triaged
-
Unknown
Description
Problem
The rollback logic on DCP disconnect is wrong. It incorrectly reports that the backup was successful and does not retry
Expectations
One of the following should happen:
- An error message should be produce saying a roll back was received
- Correctly roll back and restart the DCP stream from the beginning (This might not be a good idea because it possible the DCP stream gets disconnected again)
- Be able to resume an a DCP stream that is behind the purge seqno, assuming the purge seqno has not changed. (This might not be possible/need changes from KV_engine)
Attachments
For Gerrit Dashboard: MB-35111 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
113938,5 | MB-35111 Fail fast upon receiving a DCP rollback error | mad-hatter | backup | Status: MERGED | +2 | +1 |
114030,6 | Merge branch 'mad-hatter' into master | master | backup | Status: MERGED | +2 | +1 |