-
Type:
Bug
-
Resolution: Gone away
-
Priority:
Minor - P4
-
Affects Version/s: 1.21.0, 1.21.2
-
Component/s: Connectivity
-
None
-
Environment:Compass installed on Windows 10 Enterprise
MongoDB Enterprise Version 4.2.5 and Ops Manager 4.2.7 running on RHEL 7.0
-
Not Needed
-
None
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:
- Provide the Hostname and Port of a secondary node in the replica set
- Omit the Replica Set Name from the connection fields, then Connect
- The 'not master and slaveOk=false' error message is displayed
- Try to Disconnect from the session
- The application hangs
Note that the issue is not reproducible in 1.16.4.