A standalone or replica set started with shardsvr currently does not write a featureCompatibilityVersion on clean startup. It should write a featureCompatibilityVersion 3.4 document. This is safe, since there will be no 3.6 features to strip out if the shard is added to an FCV=3.4 cluster. This is important, because in 3.6, we require the featureCompatibilityVersion document to be present.
- is depended on by
-
SERVER-31254 Fail initial sync if fCV targetVersion is set or if there is no fCV document
-
- Closed
-
- is related to
-
SERVER-46571 Shard server replica set nodes shouldn't write config 'term' field on startup in FCV 4.2
-
- Closed
-