[SERVER-25158] Prevent a 3.2 mongos from joining a featureCompatibilityVersion("3.4") cluster Created: 19/Jul/16  Updated: 02/Dec/16  Resolved: 22/Sep/16

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

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: David Storch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-9472 Docs for SERVER-25158: Prevent a 3.2 ... Closed
Related
related to SERVER-26264 Make 3.2 mongos fail gracefully on st... Closed
related to SERVER-26265 Test that 3.2 mongos fails to join a ... Closed
related to SERVER-26261 MongoRunner.versionIterator.iterator.... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2016-08-29, Query 2016-09-19, Query 2016-10-10
Participants:

 Description   

When the featureCompatibilityVersion is 3.4, the config servers will return configsvr:2 in their isMaster response. This is a config server mode number that 3.2 mongos does not understand. This will prevent 3.2 mongos from connecting to the config servers, and thus will also prevent mongos from starting up against a featureCompatibilityVersion("3.4") cluster.



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

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-25158 prevent 3.2 mongos from connecting to a featureCompatibilityVersion 3.4 config server
Branch: master
https://github.com/mongodb/mongo/commit/e114f74a9b3bf087f15dfbee5d7250b2839308e7

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