-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Execution Team 2022-10-03
We use canAcceptWritesFor to determine if we're a primary which among other things, controls whether we should timestamp writing to the catalog. There are cases where we are writing to the catalog with a perfectly valid timestamp from an oplog entry, but we omit passing the timestamp to the transaction.
- is depended on by
-
SERVER-60753 Removing index build entries from 'config.system.indexBuilds' can make mixed mode writes
- Closed
- split to
-
SERVER-69877 Remove untimestamped writes to the catalog when restarting unfinished index builds during startup recovery
- Closed