Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.0.3, 3.1.0
-
Security Level: Public
-
Mar 9 - Mar 27
Description
If the start seqno requested is equal to snapshot end seqno, then there is no point keeping the snap_start_seqno at previous snapshot start. By doing this we can avoid unnecessary rollback.
Attachments
Issue Links
- blocks
-
MB-15886 3.1.1 Minor Release
- Resolved
For Gerrit Dashboard: MB-15826 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
53629,8 | MB-15826: Use previous ss marker snap_end as snap_start | 3.0.x | couchbase-cli | Status: MERGED | +2 | +1 |
53635,6 | MB-15826: Handle lower values of snap_st_seqno by DCP client more effectively | 3.0.x | ep-engine | Status: MERGED | +2 | +1 |
53704,2 | MB-15826: Use previous ss marker snap_end as snap_start | master | couchbase-cli | Status: MERGED | +2 | +1 |
53760,2 | MB-15826: Use new endpoint for cluster settings | master | couchbase-cli | Status: MERGED | +2 | +1 |
53775,1 | Merge remote-tracking branch 'couchbase/3.0.x' | sherlock | ep-engine | Status: MERGED | +2 | +1 |
53781,1 | Merge remote-tracking branch 'couchbase/sherlock' | sherlock | ep-engine | Status: ABANDONED | 0 | 0 |
53782,1 | Merge remote-tracking branch 'couchbase/sherlock' | master | ep-engine | Status: ABANDONED | 0 | -1 |