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

MongoDB: too many connections, exiting? #78

Open
cjlee112 opened this issue Aug 8, 2013 · 1 comment
Open

MongoDB: too many connections, exiting? #78

cjlee112 opened this issue Aug 8, 2013 · 1 comment

Comments

@cjlee112
Copy link
Owner

cjlee112 commented Aug 8, 2013

Today I found the production site giving an error message indicating no DB connection. I checked the server and found mongoDB had exited, apparently normally, no indication why.

Possibly related issue: watching the mongod messages, I see the number of open connections going up steadily (24 at present). Not sure why, or even whether this is incorrect behavior (client driver libraries tend to use connection pooling which might make this normal, at least up to a point). Conceivably, if this keeps growing and growing, it could make the server exit?

Ideas:

  • protect against mongod exit by running it from a script that just loops and restarts it.
  • research the open connections growth question
  • assess whether there's anything we could do in our code make this work better.
@cjlee112
Copy link
Owner Author

cjlee112 commented Aug 8, 2013

OK, I'm now running mongod within a while loop that will automatically restart it if it exits.

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

1 participant