Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NoRM does not work with the "mongos" process (production set up) #48

Open
ghost opened this issue Nov 4, 2010 · 2 comments
Open

NoRM does not work with the "mongos" process (production set up) #48

ghost opened this issue Nov 4, 2010 · 2 comments

Comments

@ghost
Copy link

ghost commented Nov 4, 2010

I have the following set up. 4 shards, 3 config servers, and 1 router server. NoRM does not function correctly in this situation which is a real world like set up. In my testing the NoRM driver connects through the "mongos" process instead of connecting to the "mongod" process. If I run the unit test against a single "mongod" database everything works great. If i run the unit test against the production set up, tons of tests fail. While the library is awesome, it really came as a surprise that it seems that it has never been tested in a production like set up. I really hope this is something that is fixed soon.

@ahazelwood
Copy link

I'm seeing the same issue. This also needs to take into account using replica sets as well.

@sonalsshah
Copy link

How can u connect slave database using Norm driver? Can u give me some connectionstring sample for that?

Thanks,
Sonal Shah

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants