Details
-
Bug
-
Resolution: Won't Do
-
Minor - P4
-
None
-
None
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.
Attachments
Issue Links
- is related to
-
SERVER-34342 FCV is "3.2" for new 3.4 replica set with clusterMode: shardsvr
-
- Closed
-