-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Layered Tables
-
Storage Engines - Foundations
-
700.796
-
None
-
3
WT-17905 introduced a new guard to ensure that no user data containing a "tombstone encoding" gets persisted to disk.
WiredTiger is supposed to prevent such a state by applying proper escaping to potential conflicting values; nevertheless, regressions (e.g.) started appearing while the Server CAR team was testing changes to the chunk migration infrastructure (which now includes the persistence of a recovery document to record its progress).
It is believed that the exact content of the document (and the way this gets updated) may be instrumental to reproduce the scenario.
- has to be done before
-
WT-18154 Add "non-tombstone trailing byte" assert back in
-
- Open
-
- is related to
-
-
- Closed
-
- related to
-
WT-18234 Async step-down: rely on transaction write-conflict detection, not the step-down mutex
-
- Open
-
-
-
- Open
-
-
-
- Open
-
-
-
- Closed
-