[SERVER-36442] race in autodiscover_config_rs_from_secondary.js can cause mongos to fassert Created: 03/Aug/18  Updated: 29/Oct/23  Resolved: 21/Aug/18

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-08-27
Participants:
Linked BF Score: 42

 Description   

in multiversion suites.

This happens when config servers are initially fcv latest and mongos last stable talks to a secondary which has yet to replicate the fcv to last stable.



 Comments   
Comment by Githook User [ 31/Aug/18 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-36442 Restore

{storageEngine: wiredTiger}

in autodiscover_config_rs_from_secondary.js
Branch: master
https://github.com/mongodb/mongo/commit/dc076ee0d1c4b9463084b51694957dc63f8ba593

Comment by Githook User [ 21/Aug/18 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-36442 In the mixed version tests wait for the setFCV command to be applied on all nodes
Branch: master
https://github.com/mongodb/mongo/commit/dd1c679f9e649c186e50c44b63c45474a95c0a8d

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