-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: WiredTiger
-
None
-
Storage Engines - Server Integration
-
SESIKhuuBeanz 2026-10-06
-
None
-
None
-
None
-
None
-
None
-
None
-
None
SERVER-134925 declared MongoDB's untimestamped writes to disaggregated (layered)
tables with allowOneUntimestampedWrite() so WT's commit-timestamp check
(WT-18585 / WT-18608) can be enabled. That suppresses the error, not the
problem: an untimestamped commit is never picked up by the ingest->stable drain,
so the content stays in the local ingest table and is lost when ingest is
discarded.
For each site marked TODO SERVER-134926, determine whether a real commit
timestamp can be supplied and remove the declaration where it can. Some sites run
before any timestamp exists and may need a different answer - a synthetic
bootstrap timestamp, a WT-side exemption, or doing the work before the connection
is disaggregated.
- is blocked by
-
SERVER-134925 Declare untimestamped writes to disaggregated tables via no_timestamp
-
- In Code Review
-
- is related to
-
WT-18585 Untimestamped write commits are accepted while step_down_timestamp is set
-
- Closed
-
-
SERVER-134925 Declare untimestamped writes to disaggregated tables via no_timestamp
-
- In Code Review
-
-
WT-18608 Enable the disaggregated commit timestamp check once the MongoDB failures are fixed
-
- In Code Review
-