[SERVER-43017] Wait for setFCV to propagate to all config servers Created: 23/Aug/19  Updated: 29/Oct/23  Resolved: 05/Sep/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.0.0
Fix Version/s: 4.3.1

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Misha Tyulenev
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: Sharding 2019-09-09
Participants:
Linked BF Score: 22

 Description   

The setFCV command may take longer to propagate to all nodes and this in turn can cause fassert in mongos caught in BF-13398. 
The proposed fix will add a check that all nodes on config server are actually updated st https://github.com/mongodb/mongo/blob/r4.3.0/jstests/multiVersion/genericSetFCVUsage/crash_mongos_against_upgraded_cluster.js#L33



 Comments   
Comment by Githook User [ 05/Sep/19 ]

Author:

{'email': 'misha.tyulenev@10gen.com', 'name': 'Misha Tyulenev'}

Message: SERVER-43017 wait in an integration test for setFCV to propagate to all config server nodes.
Branch: master
https://github.com/mongodb/mongo/commit/174736c49e4a284d12c2d31a3f9c8bf341a35c65

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