[COMPASS-3728] Top in performance tab times out when connected to Atlas Created: 25/Jun/19  Updated: 03/Oct/23  Resolved: 02/Dec/22

Status: Closed
Project: Compass
Component/s: Performance
Affects Version/s: 1.18.0, 1.20.0, 1.19.12
Fix Version/s: No version

Type: Bug Priority: Major - P3
Reporter: Massimiliano Marcon Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 1.19.6.png     PNG File second_time_today.png     PNG File unnamed.png    
Issue Links:
Related
related to COMPASS-3943 Update to node driver 3.3.4 Closed
is related to NODE-2274 Unified topology never regains nodes ... Closed
Documentation Changes: Not Needed
Sprint: Iteration Ostrich, Iteration Ragamuffin

 Description   

I have noticed that every now and then the performance tab shows an error: Command "top" returned error "connection to <host:port> timed out".

This typically happens when connected to Atlas.

Also reported by jeffery.schmitz.



 Comments   
Comment by Anna Henningsen [ 02/Dec/22 ]

Closing as can’t reproduce. If this is still an issue for somebody, please create a new ticket and include a Compass log file as described in https://www.mongodb.com/docs/compass/current/troubleshooting/logs/. Thank you!

Comment by Lucas Hrabovsky (Inactive) [ 12/Nov/19 ]

I suspect this has same root cause as COMPASS-3849

Comment by Wyatt Baggett [ 19/Sep/19 ]

I encounter this issue also when connected to my own 3 node replset - instead of Atlas. Each mongod processes in the replset are on v3.6.2 and I'm using Compass v1.19.6.

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