[SERVER-56688] Internal writes race with the timestamp assumptions made in oplog_writes_only_permitted_on_standalone.js Created: 05/May/21  Updated: 29/Oct/23  Resolved: 07/May/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-56687 Internal writes race with the timesta... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2021-05-17
Participants:
Linked BF Score: 140

 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.



 Comments   
Comment by Githook User [ 07/May/21 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-56688: Recalculate the highest timestamp in standalone mode in oplog_writes_only_permitted_on_standalone.js
Branch: master
https://github.com/mongodb/mongo/commit/a243d0222bd009020fe0152359536823af36f986

Generated at Thu Feb 08 05:39:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.