Details
-
Bug
-
Resolution: Fixed
-
Critical
-
6.5.0
-
None
-
Untriaged
-
Unknown
Description
during rollback, the disk snapshots across indexes/partitions could
be ahead/behind of each other due to:
a. disk snapshots may happen at different times for different indexes
or partitions as it is async.
b. during stream merge, the snapshot from INIT stream could be ahead
of snapshot in MAINT stream.
Due to this, it is important to calculate the minimum common timestamp
across indexes/partitons which could be used to restart the stream.
Attachments
| For Gerrit Dashboard: MB-35880 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 114503,3 | MB-35880 fix restartTs calculation after warmup | unstable | indexing | Status: MERGED | +2 | +1 |
| 114504,4 | MB-35880 fix restart timestamp calculation for rollback | unstable | indexing | Status: MERGED | +2 | +1 |
| 114505,1 | MB-35880 restrict usage of first snap optimization during rollback | unstable | indexing | Status: ABANDONED | 0 | 0 |
| 114506,4 | MB-35880 mark disk snap as used only for rollback to zero | unstable | indexing | Status: MERGED | +2 | +1 |