-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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 loses MongoDB connection when MongoDB server is restarted #1011
Comments
maybe you are not making your MongoDB replica set, so when the time you restart your MongoDB, the connection is dropped. Look at this link: Replication of MongoDB introduction |
Thank you! That was the problem! |
Reopening because still having issues maintaining database connection after setting up a replication set. Heres what I am doing. Step 1. 3 member replication set up and running Here is my sample format of the MongoDB connection URI: Note: using latest version of Parse-Server 2.2.0 |
@iOSDev33 does it still occur with 2.2.4? |
No response in many days, closing. |
Same problem here. The version of parse-server is 2.2.10 |
I am running a parse-server on a Digital Ocean droplet in addition to a MongoDB server on a separate Digital Ocean droplet. When i reboot or restart the MongoDB server the connection between parse-server and MongoDB is lost and requires a stop and restart of the parse-server to get things back up and running. Not sure why thats happening and is there anything to prevent it from happening? I was hoping that if the MongoDB server was ever rebooted that once it was finished parse-server would just reconnect automatically. Thanks for all the awesome work you guys are doing!
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
Environment Setup
2 Digital Ocean Droplets
1 = Parse-Server running on Digital Ocean
2 = MongoDB running on Digital Ocean
Steps to reproduce
Reboot MongoDB server or Restart MongoDB from command line
Logs/Trace
The text was updated successfully, but these errors were encountered: