You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: