-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Fully Compatible
-
ALL
-
Repl 2021-05-17
-
140
The highestTS we read from the oplog could become stale and behind the stable timestamp if there are some internal writes that happened after. And if we use that stale timestamp to insert to the oplog as a standalone, we could be writing behind the stable timestamp.
- is duplicated by
-
SERVER-56687 Internal writes race with the timestamp assumptions made in oplog_writes_only_permitted_on_standalone.js
- Closed