[SERVER-56687] Internal writes race with the timestamp assumptions made in oplog_writes_only_permitted_on_standalone.js Created: 05/May/21 Updated: 06/May/21 Resolved: 06/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Repl 2021-05-17 | ||||||||
| Participants: | |||||||||
| Description |
|
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. |