-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: 4.0.3
-
Component/s: Sharding
-
Labels:None
-
Sharding
-
ALL
-
v4.0
-
I've attached the conf files I used for my sharded cluster.
I was running this on 4.0.3-ent.
I tried running the csrs with and without inMemory (wasn't sure if it's allowed for csrs) and saw the same behavior both ways.
When I try to add the rs as a shard, I get the following:
MongoDB Enterprise mongos> db.runCommand({"addShard": "rs1/louisamac:5000,louisamac:5001,louisamac:5002", "name": "shard0"})MongoDB Enterprise mongos> db.runCommand({"addShard": "rs1/louisamac:5000,louisamac:5001,louisamac:5002", "name": "shard0"}){ "ok" : 0, "errmsg" : "can't add shard with a local copy of config.system.sessions, please drop this collection from the shard manually and try again. :: caused by :: failed to run command { drop: \"system.sessions\", writeConcern: { w: \"majority\" } } when attempting to add shard rs1/louisamac:5000,louisamac:5001,louisamac:5002 :: caused by :: NetworkInterfaceExceededTimeLimit: timed out", "code" : 96, "codeName" : "OperationFailed", "operationTime" : Timestamp(1539203544, 1), "$clusterTime" : { "clusterTime" : Timestamp(1539203544, 1), "signature" : { "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="), "keyId" : NumberLong(0) } }}
When I tried the same repro with wiredTiger, I did not see this issue.
Note: I found this while testing, not in a production or customer issue.