[DOCS-9472] Docs for SERVER-25158: Prevent a 3.2 mongos from joining a featureCompatibilityVersion("3.4") cluster Created: 02/Dec/16  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Emily Hall Assignee: Kay Kim (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-19539 Provide data in the ismaster handshak... Closed
documents SERVER-25158 Prevent a 3.2 mongos from joining a f... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Engineering Ticket 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 Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Stennie Steneker (Inactive) [ 09/Feb/17 ]

The isMaster output currently doesn't list configsvr values.

This field will only be present on config servers and indicates which config server protocol is in use:

  • 0 (or absent): original Sync Cluster Connection Config servers (SCCC); MongoDB 3.2 or earlier.
  • 1: Config Server Replica Set (CSRS) with MongoDB 3.2 feature compatibility (either MongoDB 3.2 or a deployment upgraded to 3.4 without setting featureCompatibilityVersion)
  • 2: CSRS with MongoDB 3.4 feature compatibility (either a new 3.4 install or a deployment with featureCompatibilityVersion set to 3.4 after upgrade)
Generated at Thu Feb 08 07:58:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.