[SERVER-34500] Use causal consistency in database_versioning_upgrade_downgrade.js test when reading from secondary after setFCV Created: 16/Apr/18  Updated: 29/Oct/23  Resolved: 10/Sep/18

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

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: bkp, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-09-24
Participants:
Linked BF Score: 29

 Description   

The setFCV command returns after a majority of nodes have committed the write to the FCV document, so if a client gets success for setFCV and then does a read against a secondary, that secondary may not yet be in the new FCV.



 Comments   
Comment by Githook User [ 10/Sep/18 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-34500 Wait for replication after setFCV in database_versioning_upgrade_downgrade.js
Branch: v4.0
https://github.com/mongodb/mongo/commit/ce32b09281eb8b661f4440e12fe72371d49fc2c1

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