Details
-
Bug
-
Resolution: Fixed
-
Critical
-
4.1.0, 4.5.0
-
Security Level: Public
-
None
-
Triaged
-
Unknown
Description
Ep-engine is building parameters for new stream (and perhaps creating as well) when the existing stream (in the same or another consumer connection) for that vbucket is still around and the items in that stream is being processed. When the existing stream is being closed, the stream is set to dead state and then the items in the stream is cleared. There is a small window between the stream being set to dead state and the items being cleared, where a new stream parameters are built and hence wrong snapstart seqno and start seqno is sent to producer in the stream request.
Attachments
Issue Links
- relates to
-
-
- Closed
-
| For Gerrit Dashboard: MB-17273 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 58362,1 | MB-17273: Make add stream and close stream operations atomic. | master | ep-engine | Status: ABANDONED | 0 | 0 |
| 58364,1 | MB-17273: Make add stream and close stream operations atomic. | 3.0.x | ep-engine | Status: ABANDONED | -1 | +1 |
| 58366,1 | MB-17273: Atomically transition to dead state on receiving DCP_STREAM_END. | 3.0.x | ep-engine | Status: ABANDONED | -1 | +1 |
| 58367,2 | MB-17273: Stop processing the passive stream buffer when it goes to DEAD state. | 3.0.x | ep-engine | Status: ABANDONED | -1 | +1 |
| 58495,5 | MB-17273: Ensure stream state does not change when buffered items are processed | master | ep-engine | Status: ABANDONED | -2 | +1 |
| 58774,6 | MB-17273: Ensure that passive stream buffer is not processed after it is DEAD. | master | ep-engine | Status: MERGED | +2 | +1 |
| 59286,2 | MB-17273: Update bytes processed correctly in passive str when buffer is cleared | master | ep-engine | Status: MERGED | +2 | +1 |