Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
6.5.0, 6.0.3, 6.0.4, 6.5.1, 6.6.0
-
Triaged
-
1
-
Yes
Description
Problem
As described in CBSE-8828, for a replica DCP stream. If a previous item that uses XATTRs is to be deleted, however it is not resident - then we must perform a bgfetch - see MB-36087. When the bgfetch is complete we replay PassiveStream::messageReceived. However this time it fails because the last seqno now equals the sequence number of the deletion and so it is discarded.
Suggested Possible Solution
- only set the last seqno to the seqno of the message just received, once the message has been completed or
- If an EWOULD_BLOCK occurs reserve the setting of the last seqno so the message can be received again.
Attachments
Issue Links
1.
|
[BP] MB-41255 to 6.0.4 - MP2 |
![]() |
Resolved | Daniel Owen |
Thanks Dave Rigby.
Customer was upgrading from 6.0 to 6.6. Given that the fix was backported to 6.0.5 also, looks like the issue existed in 6.0.x as well. Likely that the customer was not using XATTRs and their previous upgrades (to 6.0.x) were hence not impacted. So yes, probably not a regression.