[SERVER-39070] The shell wrongly marks connections as idle Created: 17/Jan/19  Updated: 07/Mar/19  Resolved: 07/Mar/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Alyson Cabral (Inactive) Assignee: Mathias Stearn
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-39186 Shell should strip trailing dot from ... Closed
duplicates SERVER-7741 Suppress ReplicaSetMonitorWatcher log... Closed
Operating System: ALL
Sprint: Service Arch 2019-01-28, Service Arch 2019-02-11, Service Arch 2019-02-25, Service Arch 2019-03-11
Participants:

 Description   

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.



 Comments   
Comment by Mathias Stearn [ 07/Mar/19 ]

The problems described in this ticket are being resolved by the combination of the two linked tickets.

Comment by Asya Kamsky [ 17/Jan/19 ]

Can confirm.

2019-01-17T16:49:21.913-0500 I ASIO     [ReplicaSetMonitor-TaskExecutor] Dropping all pooled connections to pytpcc-shard-00-00-hakmv.gcp.mongodb.net.:27017 due to NetworkInterfaceExceededTimeLimit: Connection pool has been idle for longer than the host timeout
2019-01-17T16:49:21.917-0500 I ASIO     [ReplicaSetMonitor-TaskExecutor] Dropping all pooled connections to pytpcc-shard-00-02-hakmv.gcp.mongodb.net.:27017 due to NetworkInterfaceExceededTimeLimit: Connection pool has been idle for longer than the host timeout
2019-01-17T16:49:21.923-0500 I ASIO     [ReplicaSetMonitor-TaskExecutor] Dropping all pooled connections to pytpcc-shard-00-01-hakmv.gcp.mongodb.net.:27017 due to NetworkInterfaceExceededTimeLimit: Connection pool has been idle for longer than the host timeout
 

Never seen this before. In fact, ASIO subsystem appeared new - didn't see it in 4.1.4 shell.

Generated at Thu Feb 08 04:50:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.