Details
-
Bug
-
Resolution: Fixed
-
Critical
-
7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.1.4, 7.0.5, 7.1.0, 7.1.1, 7.1.2, 7.2.0, 7.1.3, 7.2.1, 7.1.5, 7.2.2
-
Untriaged
-
0
-
Unknown
Description
XDCR doesn't handle rollback requests during stream-end scenarios and never reinitializes DCP stream (https://github.com/couchbase/kv_engine/blob/dc00b746e5f22cc408acd179239430cac66f2b17/docs/dcp/documentation/commands/stream-end.md?plain=1#L52[…]C12)
Once stream-end with rollback flag is received for a vb, we are not able to get any mutations to be replicated for that vb anymore, unless the pipeline is restarted which causes the streams to reinitialize.
Attachments
Issue Links
- backports to
-
-
- Closed
-
| For Gerrit Dashboard: MB-59233 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 199235,3 | MB-59233: Populate flags for the stream-end uprEvent | master | gomemcached | Status: MERGED | +2 | +1 |
| 199418,10 | MB-59233: Restart main pipeline if stream-end is received in Dcp_Stream_Active state | master | goxdcr | Status: MERGED | +2 | +1 |