[DOCS-11551] New 3.4 replica set with shardsvr option reports FCV as 3.2 until added to cluster Created: 06/Apr/18  Updated: 30/Oct/23

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

Type: Bug Priority: Minor - P4
Reporter: Spencer Brown Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-34342 FCV is "3.2" for new 3.4 replica set ... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

3.4 doc page on Backwards Incompatible Features says that new deployments default to FCV 3.4. There is a case where they do not.

That case is when you deploy a brand new 3.4 replica set in preparation for adding it to a sharded cluster, in other words, you have the sharding.clusterRole: shardsvr option set. In this case, the FCV is reported as "3.2" until the replica set is added to the sharded cluster, at which point it will be set to the FCV of the sharded cluster as a whole. See SERVER-34342 for details.

This probably applies to 3.6 also but I have not tested that.



 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!

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