Details
-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Untriaged
-
1
-
Unknown
Description
On kv node failure, DCP consumer may not be able to resume from where it left.
DCP producer asks DCP consumer to rollback to certain sequence number and history since requested vbucket history won't be available on failed kv node. In this scenario, DCP consumer will rollback to 0 and eventing will start stream from 0.
Starting stream from 0 can be avoided in certain situation by retrying stream with previous vbucket history.
Attachments
Issue Links
- is a backport of
-
MB-49720 CBSE - Rollback handling - Retry with previous uuid on rollback message
- Closed