[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: |
|
||||||||||||
| 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:
|