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
For Gerrit Dashboard: MB-62190 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
210936,4 | MB-62190: minor improvements | neo | analytics-dcp-client | Status: MERGED | +2 | +1 |
210937,8 | MB-62190: only rollback datasets involved in stream on KV rollback | 7.2.5 | cbas-core | Status: MERGED | +2 | +1 |
211085,1 | MB-62190,MB-55805: merge branch '7.2.5' into 'neo' | neo | cbas-core | Status: MERGED | +2 | +1 |
211088,1 | MB-62190,MB-55805,MB-62129: merge branch 'neo' into 'trinity' | trinity | analytics-dcp-client | Status: MERGED | +2 | +1 |
211089,1 | MB-62190,MB-55805,MB-62129: merge branch 'neo' into 'trinity' | trinity | cbas-core | Status: MERGED | +2 | +1 |