Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Storage Execution
-
Fully Compatible
-
Execution Team 2024-01-22, Execution Team 2024-02-05
-
166
Description
Right now we're maintaining the current behaviour where if bucket compression fails, we leave the bucket uncompressed. When bucket compression fails, chances are the bucket is corrupt in some way, and further writes to it could result in data loss. Instead, we should fail the insert, close the bucket, and retry the insert without re-opening buckets. We cannot re-open buckets as we can end up in a scenario where we keep retrying the insert in the same bucket. We'll also need to limit the number of retries.
Attachments
Issue Links
- is related to
-
SERVER-86073 Add a way to track whether the number of frozen time-series buckets is increasing
-
- Open
-
-
SERVER-86087 Evaluate whether frozen time-series buckets can ever stop being tracked
-
- Backlog
-
-
SERVER-86072 Retry when time-series bucket compression fails for unordered inserts
-
- In Progress
-
-
SERVER-86085 Improve naming/semantics around frozen time-series buckets and reopening
-
- Backlog
-
- related to
-
SERVER-84234 BSONColumnBuilder throwing should be handled gracefully
-
- Open
-