[COMPASS-4235] Support discovering deployment topology Created: 10/Apr/20  Updated: 11/May/20  Resolved: 11/May/20

Status: Closed
Project: Compass
Component/s: Connectivity
Affects Version/s: 1.20.5
Fix Version/s: No version

Type: New Feature Priority: Major - P3
Reporter: Oleg Pudeyev (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
UserVoice Links:

Support discovering deployment topology (Suggestion)
No Status (1 users)


 Description   

It appears that Compass has no provision to discover the topology of deployment, and instead it requires the user to specify replica set name in order to connect to a replica set.

This was mentioned on SO here: https://stackoverflow.com/questions/61135528/mongodb-compass-forces-me-to-enter-replica-set-name-when-trying-to-connect-to-my/61135731#61135731

For example when I connected to mongodb://localhost:27020 where the node at 27020 is a secondary, I received this message:

> 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.

As a user of Compass, I would like to specify the minimum required information for Compass to connect to my deployment. In case of a replica set, this is the address of a single node and I would like Compass to automatically determine set name and connect to all other nodes per the SDAM specification.

Note that topology discovery for drivers has recently been specified in SPEC-1248.



 Comments   
Comment by Massimiliano Marcon [ 11/May/20 ]

Not something we are considering in the short term. Having said that, I posted this idea to user voice which is where we track feature requests.

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