-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.0.8
-
Component/s: Networking, Sharding
-
None
-
Environment:Debian Wheezy
-
Linux
-
Last week we had to make maintenance on server hardware where is one of the config servers. After server shutdown we had problems with timeouts on connections to mongos.
From tests on staging environment:
normal state
-> time echo "db.system.version.find()" | mongo --username=someuser --password=somepassword admin MongoDB shell version: 3.0.8 connecting to: admin { "_id" : "authSchema", "currentVersion" : 5 } bye real 0m0.149s user 0m0.110s sys 0m0.030s }}
degraded state (one server down) -> time echo "db.system.version.find()" | mongo --username=someuser --password=somepassword admin MongoDB shell version: 3.0.8 connecting to: admin { "_id" : "authSchema", "currentVersion" : 5 } bye real 0m38.845s user 0m0.130s sys 0m0.050s
- duplicates
-
SERVER-21531 Shard's connection blocks forever when attempting autosplit and first config server (SCCC) in TCP blackhole from shards
- Closed