Robomongo: Robomongo reuses replicaset hostnames if there's two configurations with same replicaset name and different hosts

[mahe-work]

I ran into a VERY dangerous situation that seems to be related to the problem in issue #1288 but I feel that this merits its own issue that should be red flagged!

We have test and production replica sets, which have same replica set name but different hosts. I have created replica set configurations for these in Robomongo, and edited the robomongo.js as instructed in #1288

Now, if I connect to production replica set first, and then to test replica set, Robomongo seems to remember production replica set hostnames and uses those to seemingly connect to test replica set!! I end up in a situation where at a glance it seems that I'm doing things in test environment but in reality I'm connected to production!!

I myself have stopped using Robomongo because of this and I will be instructing people that I've recommended Robomongo to do the same until this is fixed.

[simsekgokhan]

Hi @mahe-kl , thanks for reporting the problem.

I totally agree with you that this issue should be red-flagged which has already been.
The issue is actually not related to issue #1288 but this one https://github.com/paralect/robomongo/issues/1291#issuecomment-284435407. You can see the root cause of the problem if you like which comes from MongoDB design intent.

Having said that we are already thinking how to avoid this critical problem. We will have to change the mongo design which will not be very easy.

For now, I can suggest to use https://studio3t.com/, which you might already have heard that we are now under the same organization.

[mahe-work]

Thanks for clarification. I'll give studio3t a try.

[simsekgokhan]

No problem. An update about this issue, we have already included a fix and error message to prevent this problem. But for now replica sets with same set name will be supported only on different instances of Robomongo, which means you have to open two Robomongo, one for production and one for your test.

The fix is planned to be included in the next release Robomongo 1.0.

[mahe-work]

I just tried 1.0, and I get error message clearly stating that there is same replicaset name with different members. Another instance is able to connect. Works for me, thank you! :+1:

[simsekgokhan]

Very happy to hear that it works. I will close this ticket now. Feel free to open for any reason. Best Regards.

[simsekgokhan]

Fixed in Robomongo 1.0.

[trentpattern]

3 years later and still having issues with this

[Harimed]

I had the same issue today