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

Closed
mahe-kl opened this Issue Mar 14, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@mahe-kl

mahe-kl commented Mar 14, 2017

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 simsekgokhan added the major label Mar 15, 2017

@simsekgokhan

This comment has been minimized.

Show comment
Hide comment
@simsekgokhan

simsekgokhan Mar 15, 2017

Collaborator

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 #1291 (comment). 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.

Collaborator

simsekgokhan commented Mar 15, 2017

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 #1291 (comment). 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-kl

This comment has been minimized.

Show comment
Hide comment
@mahe-kl

mahe-kl Mar 27, 2017

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

mahe-kl commented Mar 27, 2017

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

@simsekgokhan

This comment has been minimized.

Show comment
Hide comment
@simsekgokhan

simsekgokhan Mar 27, 2017

Collaborator

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.

Collaborator

simsekgokhan commented Mar 27, 2017

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

This comment has been minimized.

Show comment
Hide comment
@mahe-kl

mahe-kl Apr 24, 2017

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! 👍

mahe-kl commented Apr 24, 2017

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! 👍

@simsekgokhan

This comment has been minimized.

Show comment
Hide comment
@simsekgokhan

simsekgokhan Apr 26, 2017

Collaborator

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

Collaborator

simsekgokhan commented Apr 26, 2017

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

@simsekgokhan

This comment has been minimized.

Show comment
Hide comment
@simsekgokhan

simsekgokhan Apr 26, 2017

Collaborator

Fixed in Robomongo 1.0.

Collaborator

simsekgokhan commented Apr 26, 2017

Fixed in Robomongo 1.0.

simsekgokhan added a commit that referenced this issue Apr 26, 2017

ReplicaSets: #1302 - To avoid the problem when same set name is used …
…with different members, which is not supported configuration, Robomongo might connect to wrong set.

simsekgokhan added a commit that referenced this issue Apr 26, 2017

ReplicaSets: #1302: Some enhancements and more informational error me…
…ssages for the issue where same set name is used with different members.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment