-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
-
Service Arch 2019-01-28, Service Arch 2019-02-11, Service Arch 2019-02-25, Service Arch 2019-03-11
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
Using a fairly current shell from master, I have an active find running and my connections still get marked as idle. See output below.
MongoDB shell version v4.1.6-545-g3b4c6a6
connecting to: mongodb:.../test?authSource=admin&gssapiServiceName=mongodb&replicaSet=Production0-shard-0&ssl=true
2019-01-17T13:58:07.625-0500 I NETWORK [js] Starting new replica set monitor for Production0-shard-0/production0-shard-00-02-fpppp.mongodb.net.:27017,production0-shard-00-01-fpppp.mongodb.net.:27017,production0-shard-00-00-fpppp.mongodb.net.:27017
2019-01-17T13:58:07.626-0500 I ASIO [ReplicaSetMonitor-TaskExecutor] Connecting to production0-shard-00-01-fpppp.mongodb.net.:27017
2019-01-17T13:58:07.626-0500 I ASIO [ReplicaSetMonitor-TaskExecutor] Connecting to production0-shard-00-02-fpppp.mongodb.net.:27017
2019-01-17T13:58:07.626-0500 I ASIO [ReplicaSetMonitor-TaskExecutor] Connecting to production0-shard-00-00-fpppp.mongodb.net.:27017
2019-01-17T13:58:07.733-0500 I ASIO [ReplicaSetMonitor-TaskExecutor] Connecting to production0-shard-00-00-fpppp.mongodb.net:27017
2019-01-17T13:58:07.770-0500 I NETWORK [ReplicaSetMonitor-TaskExecutor] changing hosts to Production0-shard-0/production0-shard-00-00-fpppp.mongodb.net:27017,production0-shard-00-01-fpppp.mongodb.net:27017,production0-shard-00-02-fpppp.mongodb.net:27017 from Production0-shard-0/production0-shard-00-00-fpppp.mongodb.net.:27017,production0-shard-00-01-fpppp.mongodb.net.:27017,production0-shard-00-02-fpppp.mongodb.net.:27017
2019-01-17T13:58:07.771-0500 I ASIO [ReplicaSetMonitor-TaskExecutor] Connecting to production0-shard-00-02-fpppp.mongodb.net:27017
2019-01-17T13:58:07.771-0500 I ASIO [ReplicaSetMonitor-TaskExecutor] Connecting to production0-shard-00-01-fpppp.mongodb.net:27017
Implicit session: session { "id" : UUID("be4fd519-7c9b-4d63-93e9-1b57628f597b") }
MongoDB server version: 3.6.9
WARNING: shell and server versions do not match
MongoDB Enterprise Production0-shard-0:PRIMARY> use euphonia
switched to db euphonia
MongoDB Enterprise Production0-shard-0:PRIMARY> show collections
Warning: unable to run listCollections, attempting to approximate collection names by parsing connectionStatus
pings
MongoDB Enterprise Production0-shard-0:PRIMARY> db.pings.find({"clusterId" : "-"})
2019-01-17T14:03:07.738-0500 I ASIO [ReplicaSetMonitor-TaskExecutor] Dropping all pooled connections to production0-shard-00-02-fpppp.mongodb.net.:27017 due to NetworkInterfaceExceededTimeLimit: Connection pool has been idle for longer than the host timeout
2019-01-17T14:03:07.738-0500 I ASIO [ReplicaSetMonitor-TaskExecutor] Dropping all pooled connections to production0-shard-00-01-fpppp.mongodb.net.:27017 due to NetworkInterfaceExceededTimeLimit: Connection pool has been idle for longer than the host timeout
2019-01-17T14:03:07.773-0500 I ASIO [ReplicaSetMonitor-TaskExecutor] Dropping all pooled connections to production0-shard-00-00-fpppp.mongodb.net.:27017 due to NetworkInterfaceExceededTimeLimit: Connection pool has been idle for longer than the host timeout
I see this error fairly regularly.
- duplicates
-
-
- Closed
-
-
SERVER-7741 Suppress ReplicaSetMonitorWatcher logging from the shell
-
- Closed
-