Details
-
Bug
-
Resolution: Fixed
-
Major
-
7.2.5, 7.6.1
-
Untriaged
-
0
-
Unknown
Description
In the event that KV indicates on a stream request that we need to rollback, today we rollback all datasets in the bucket- this is a leftover from before streams were utilized (pre-collections). It could be the case that only the collection(s) covered by that particular stream need to be rolled back. Rolling back all collections on the bucket results in unnecessary re-streaming of all collections from KV.
The logic should be refined to only truncate collection(s) affected by the rollback response from KV.
Attachments
Issue Links
- causes
-
MB-62504 Ingestion is rollbacking to 0 multiple times during scaling operations. Ingestion jobs are getting aborted/restarted
- Closed