[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: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| 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. |