[SERVER-42225] timestamped_reads_wait_for_prepare_oplog_visibility.js should insert documents with write concern majority to guarantee visibility in transactions Created: 12/Jul/19  Updated: 15/Jul/19  Resolved: 15/Jul/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Jason Chan Assignee: Jason Chan
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-41769 The committedSnapshot should not be g... Closed
Operating System: ALL
Sprint: Repl 2019-07-29
Participants:
Linked BF Score: 13

 Description   

It is possible for timestamped_reads_wait_for_prepare_oplog_visibility.js to fail if the writes we do are ahead of the all committed timestamp and do not make it into the transaction. This is much more likely in suites like logical_session_cache_replication_100ms_refresh because that suite runs a lot of background operations like the LogicalSessionCacheReaper that could hold back the write from making it into the all committed.

We should have these inserts be written with majority write concern to guarantee that they will make it into the all committed snapshot.



 Comments   
Comment by Jason Chan [ 15/Jul/19 ]

judah.schvimer Yes you're right. I can mark this as a duplicate of SERVER-41769.

Comment by Judah Schvimer [ 15/Jul/19 ]

jason.chan, is this related to the audit for SERVER-41769?

Generated at Thu Feb 08 04:59:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.