[COMPASS-3849] Compass loses connection after a while Created: 28/Aug/19  Updated: 29/Oct/23  Resolved: 13/Nov/19

Status: Closed
Project: Compass
Component/s: Connectivity
Affects Version/s: None
Fix Version/s: 1.20.0

Type: Bug Priority: Major - P3
Reporter: Massimiliano Marcon Assignee: Lucas Hrabovsky (Inactive)
Resolution: Fixed Votes: 6
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2019-08-28-14-40-46-286.png     PNG File image-2019-08-28-14-41-23-763.png    
Issue Links:
Depends
depends on COMPASS-3943 Update to node driver 3.3.4 Closed
Related
is related to NODE-2274 Unified topology never regains nodes ... Closed
Sprint: Iteration Python, Iteration Ragamuffin

 Description   

I left Compass open and connected to the data-sets Atlas cluster for a couple of hours while I did other things and had lunch.

When I tried to use it again, I clicked on a collection and got this (note also the cluster info on the left, where it says 0 nodes):

Cmd+R led to this:



 Comments   
Comment by Oliver Greil [ 02/Sep/19 ]

Follow up: If you have a self hosted mongodb instance then you don't get this "server timeout" error instead you get: "Server instance pool was destroyed". But it's the same it only happens if you leave compass open for a while.

Comment by Oliver Greil [ 02/Sep/19 ]

I can confirm this issue! However it only seems to happen when you are connecting over the internet to a mongodb instance. When using Compass locally on the same machine as the instance, this does not happen.

Generated at Wed Feb 07 22:34:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.