[COMPASS-4330] Compass Hangs When Disconnecting From a Connection to a Secondary Created: 22/Jun/20  Updated: 27/Oct/23  Resolved: 17/May/22

Status: Closed
Project: Compass
Component/s: Connectivity
Affects Version/s: 1.21.0, 1.21.2
Fix Version/s: 1.31.0

Type: Bug Priority: Minor - P4
Reporter: maia hariri Assignee: Unassigned
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Compass installed on Windows 10 Enterprise
MongoDB Enterprise Version 4.2.5 and Ops Manager 4.2.7 running on RHEL 7.0


Documentation Changes: Not Needed

 Description   

Hello,

I am testing the latest stable version of MongoDB Compass on our existing deployments and am noticing some cases where the application hangs. 

For this particular issue, I am connecting to a 3 member replica set and testing the case where the user omits the replica set name in the connections details, specifies the host and port of a secondary member, and uses the default Primary Read Preference.

 

To reproduce:

  1. Provide the Hostname and Port of a secondary node in the replica set
  2. Omit the Replica Set Name from the connection fields, then Connect
  3. The 'not master and slaveOk=false' error message is displayed
  4. Try to Disconnect from the session
  5. The application hangs

 

Note that the issue is not reproducible in 1.16.4.



 Comments   
Comment by Rhys Howell [ 17/May/22 ]

Thanks for reporting! This was fixed as part of the connectivity work. Going to close, feel free to reopen if you update and find the issue persists.

Comment by Jessica Sigafoos [ 23/Sep/21 ]

Hi maia.hariri@sunlife.com, are you still seeing this in the most recent version of Compass (1.28.4)?

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