-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
As of SERVER-58410 (5.3+) all writes that are done to the replset.minvalid collection are untimestamped.
However, to this date we are still treating the collection as one that is using timestamp-based durability.
In the event we perform even one write with a timestamp to the collection then WT would complain about a timestamp ordering violation on the next write.
We should consider removing the exception from our code so that the collection is treated as a normal untimestamped local db collection and indicate to WT that untimestamped writes are acceptable.
- is related to
-
SERVER-58410 Discontinue writing to appliedThrough/minValid as part of secondary batch application
-
- Closed
-