Open dt opened 2 months ago
@yuzefovich I didn't get a chance to look at this during my on-call rotation. If you get a chance, could you please take a look? Thank you!
(quoting @yuzefovich during triage)
We think a way to reproduce this is to:
- Set a short GC TTL on the range
- make the import take longer than the TTL,
- and then cause the import to fail, and it seems like that might hit this assertion
@dt does it seem possible that this issue is caused by #91151?
Observed on drt-ua2, running
A0AF5664
: the initial import failed after several days, and now appears stuck and unable to revert:The DB console reports no unavailable ranges.
Jira issue: CRDB-37824