-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Storage Execution
-
ALL
-
-
Storage 2017-10-02
Brought up a replica set with --shardsvr on 3.5.13. After the members are all healthy, the FCV is defaulted to 3.4 on all shard members.
This then causes problems when I try to run sharding commands on the cluster :
mongos> db.runCommand({"shardCollection" : "MMS-AUTO_TEST_DIR.coll1", "key" : {"a" : 1}}) { "ok" : 0, "errmsg" : "expected primary shard to return a UUID for collection MMS-AUTO_TEST_DIR.coll1 as part of 'info' field but got { name: \"coll1\", type: \"collection\", options: {}, info: { readOnly: false }, idIndex: { v: 2, key: { _id: 1 }, name: \"_id_\", ns: \"MMS-AUTO_TEST_DIR.coll1\" } }", "code" : 1, "codeName" : "InternalError", "$clusterTime" : { "clusterTime" : Timestamp(1505837355, 6), "signature" : { "hash" : BinData(0,"kXw/D8QqlXe1+EjeDFwGcSpd0Uc="), "keyId" : NumberLong("6467521737553608705") } }, "operationTime" : Timestamp(1505837355, 6) }
Esha identified that these are because the shard members are on FCV=3.4, but the rest of the cluster are on FCV=3.6.
(Note: not sure if this is intended behavior or not, but Maria mentioned I should file a ticket. Happy to adjust our tests to accommodate if this is intended behavior)