[COMPASS-4067] Issue when connecting to / disconnecting from secondary with wrong settings Created: 06/Jan/20  Updated: 29/Oct/23  Resolved: 02/Mar/20

Status: Closed
Project: Compass
Component/s: Connectivity
Affects Version/s: 1.20.1
Fix Version/s: 1.21.0

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

Attachments: File PastedGraphic-1.tiff     PNG File Screenshot 2020-03-02 12.27.45.png    

 Description   

Reported by jeffrey.sposetti.

Steps to repro

  • Point to a secondary but set read pref primary
  • You’ll get the error in the screenshot (which is fine).
  • Try to “Disconnect” from the menu and things just spin / get stuck.
  • Need to close Compass OR select Connect to… from menu to get out of this spinning stuck state.


 Comments   
Comment by Lucas Hrabovsky (Inactive) [ 02/Mar/20 ]

Fixed by driver's 3.4 SDAM rewrite. Repro:

npm i -g mongodb-runner;
 
MONGODB_TOPOLOGY=replicaset \
MONGODB_VERSION=stable \
mongodb-runner start
 
# RS started with primary on localhost:27017 and secondaries on localhost:27018 and localhost:27019 

Connecting to secondary directly with readPreference=primary and then Disconnect from the Application menu worked as expected without any spinning.

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