[SERVER-34890] Use rst.awaitLastOpCommitted() in secondary_reads_timestamp_visibility.js to correctly wait for the secondary to catch up Created: 08/May/18  Updated: 29/Oct/23  Resolved: 08/May/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 3.7.9
Fix Version/s: 4.0.0-rc0

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-05-21
Participants:
Linked BF Score: 0

 Description   

The test secondary_reads_timestamp_visibility.js uses awaitReplication to wait for the secondary to catch up to the majority commit point. This can cause failures return incorrect results when doing majority reads on the secondary.

The test should be modified to use awaitLastOpCommitted instead, which guarantees the secondary has committed the last oplog on the primary.



 Comments   
Comment by Githook User [ 08/May/18 ]

Author:

{'email': 'louis.williams@mongodb.com', 'name': 'Louis Williams', 'username': 'louiswilliams'}

Message: SERVER-34890 Use awaitLastOpCommitted for secondary_reads_timestamp_visibility.js
Branch: master
https://github.com/mongodb/mongo/commit/3943887a80e35fdf9fbfa2149b5a6c5c4ec5f587

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