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

parse server with an n-node mongo set up #1222

Closed
goggelj opened this issue Mar 28, 2016 · 1 comment
Closed

parse server with an n-node mongo set up #1222

goggelj opened this issue Mar 28, 2016 · 1 comment

Comments

@goggelj
Copy link

goggelj commented Mar 28, 2016

If I am using a 3-node cluster, what should DB URI look like?

I am asking as according to mlab, I should run tests to cover primary node failure. Can't do that until I can successfully configure a 3-node cluster for my Parse instance.

Also, is there a number of users I need to consider before moving away from a single node?

For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

Environment Setup

Steps to reproduce

Logs/Trace

@drew-gross
Copy link
Contributor

Once you have setup a cluster, mLab should give you the URI for it. If setting up your own cluster, not on mLab, check the mongodb docs (basically, you supply each domain and port in a comma separated list in the "URI")

Whether to switch away from a single node depends more on whether you need redundancy in your database than the number of users you have.

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