SERVER-42185 is a fix for such an untimestamped write in a certain path. However, to prevent such mistakes in the future, we need a way to detect these unintentional untimestamped writes, so that the bug shows up sooner than caught by other checks such as dbhash mismatch which requires a chain of reaction after the untimestamped writes.
- depends on
-
SERVER-42718 dropDatabase commands can be run concurrently, leading to an invalid state
- Closed
-
SERVER-42834 Adding a namespace to the drop pending reaper is not RecoveryUnit::abortUnitOfWork safe
- Closed
-
SERVER-42830 Applying a rename operation can result in multiple WT transactions
- Closed
- is related to
-
SERVER-43018 Formalize contract for safely accessing the catalog
- Closed
-
SERVER-44359 Race between oplog visibility thread and timestamped inserts in dbtest repl
- Closed