Details
-
Bug
-
Resolution: Fixed
-
Critical
-
None
Description
This is to limit the amount of data that needs to catch up upon KV data loss.
Indexer currently keeps only the latest vbuuid in the timestamp. Indexer could store 2-3 vbuuids in-memory if the seqno has not changed between those(and possibly persist in disk snapshot as well). If DCP asks to rollback to 0, indexer can first retry with stream request with the stored vbuuids before going to disk snapshots.
Attachments
Issue Links
- relates to
-
MB-32227 Improve dcp rollback handling
- Closed