Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
ReplicaSet Name is not configurable on UI #1288
Hi @Swissbite , first of all "setName" in the config file, is the cached set name and internal usage only for faster connections. And, it needs be called "cachedSetName", we will do this change probably in the next releases to avoid future confusions.
Normally, it should be possible to connect without set name. For example mongo atlas cloud service is connectable from Robomongo without entering set name.
I will tag this issue as 'critical', since you are unable to connect and do your work.
Thanks a lot, that public set made investigation much faster.
First of all, I have reproduced the problem, seems like the problem is Robomongo cannot learn the set name which is a critical information for connections to replica sets. We will investigate this, seems like a major problem at first look at the code. This is the cause of this problem:
So, if a user that can execute "rs.status()" command is used, I believe Robomongo will be able to connect.
Seems like you were on the correct way, the cached set name saves the day.
I was able to connect after these steps.
I can't connect to my free Atlas cluster.
"setName" isn't helping too.
Hi @altairzuzu , thanks for reporting the issue.
For me then explanation was not very clear, so here is my addition:
referenced this issue
Mar 14, 2017
Hi @danafreer , sorry for the delay, we have decided to include (and already included) 4-5 fixes and enhancements into next version 1.0 which will have set name configurable on UI. And it is being tested now. ETA is next week. We will probably start coding for 3.4 support next week after release.
Just checked Robomongo 1.1 under windows 10 x64 - works fine with Atlas replica set.
Connect url, which provided to you by atlas, looks like:
In SSL tab I specified
With such configuration robomongo 1.1.0-beta connects fine to MongoDB Atlas.