This assert, introduced in WT-17905, has exposed issues with how we encode tombstones, resulting in BF-44719 and BF-44591.
The long term fix is to complete WT-18057 and WT-17933.
For now, remove the assert to enable mitigation of the BFs. While the assert is correct and points at a real issue, broken-encoded entries "work by accident" in Mongo because of the way Mongo decodes BSON.
- is related to
-
WT-17933 Stop persisting encoded ingest tombstones prefixed values on disk
-
- Blocked
-
-
WT-17905 Layered follower: user value equal to tombstone bytes is read back as deleted
-
- Closed
-
-
WT-18057 Layered tombstone decode guard triggered while persisting the recovery doc of an inflight chunk operation
-
- Investigating
-
- related to
-
WT-18154 Add "non-tombstone trailing byte" assert back in
-
- Open
-