[COMPASS-2796] SSH tunnel to Atlas cluster SECONDARY fails Created: 30/Apr/18  Updated: 13/Nov/19  Resolved: 13/Nov/19

Status: Closed
Project: Compass
Component/s: Compass, Connectivity, Security
Affects Version/s: 1.13.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Brian Blevins Assignee: Lucas Hrabovsky (Inactive)
Resolution: Duplicate Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File request_for_secondary_connection_fails.png     PNG File valid_secondary_connection_to_M001_student_cluster.png    
Issue Links:
Related
is related to COMPASS-2744 Stuck in "loading navigation": db.adm... Closed

 Description   

Attempting to use the SSH tunnel option in Compass to connect to an Atlas cluster secondary member fails. Even if the user identifies a secondary member for the connection and specifies a read preference of "Secondary", the following error is displayed.

An error occurred while loading navigation: 'not master and slaveOk=false': It is recommended to change your read preference in the connection dialog to Primary Preferred or Secondary Preferred or provide a replica set name for a full topology connection.

Note that while there are special restrictions on M0 (free tier) clusters, the example in the screenshots is an M30 cluster.



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

COMPASS-2744

Comment by Brian Blevins [ 11/Sep/18 ]

Inability to connect to secondaries is a problem with SSH because the primary may/will change due to an election.

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