[SERVER-26363] Await replication after setting the featureCompatibilityVersion to 3.2 on the CSRS started by ShardingTest Created: 27/Sep/16  Updated: 19/Nov/16  Resolved: 28/Sep/16

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

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Done 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: TIG 2016-10-10
Participants:
Linked BF Score: 0

 Description   

mongos uses the ReadPreference::Nearest read preference when initializing the config version on start-up. This leaves a window open where we've set the featureCompatibilityVersion to 3.2 on a majority of our config server nodes, but mongos chooses to read from a node that hasn't applied the update the admin.system.version collection and fails sees that the featureCompatibilityVersion is 3.4.

We should update ShardingTest to await replication of the CSRS after setting the featureCompatibilityVersion of the CSRS to 3.2. This will ensure that mongos can connect to any of the nodes in the CSRS because they will all have featureCompatibilityVersion=3.2.



 Comments   
Comment by Githook User [ 28/Sep/16 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-26363 Await replication of the CSRS after setting fCV to 3.2.
Branch: master
https://github.com/mongodb/mongo/commit/520f5571d039b57cf9c319b49654909828971073

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