[SERVER-38650] secondary_reads_timestamp_visibility.js must wait for operations to be applied on secondary Created: 14/Dec/18  Updated: 29/Oct/23  Resolved: 17/Dec/18

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

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
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: Repl 2019-01-14
Participants:
Linked BF Score: 20

 Description   

In secondary_reads_timestamp_visibility.js, we wait for the secondary's readConcernMajorityOpTime to advance, then read from the secondary. However, when majority read concern is disabled, the readConcernMajorityOpTime is set based on the node's knowledge of the majority commit point and does not imply that the node has applied through that point. This causes us to read from the secondary before it has applied the operations. We must also wait for the secondary to apply the operations.



 Comments   
Comment by Githook User [ 17/Dec/18 ]

Author:

{'username': 'tessavitabile', 'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile'}

Message: SERVER-38650 secondary_reads_timestamp_visibility.js must wait for operations to be applied on secondary
Branch: master
https://github.com/mongodb/mongo/commit/cce23861d5a0141b556b3d476812d8d5ded71d5d

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