4 ms·
Among reasons, I see stuff like this: "Appearantly someone set the connection timeout to 9000 secs which means a connection to a MongoDB instance through Netsca
by jeswin 15y ago
Among reasons, I see stuff like this:
"Appearantly someone set the connection timeout to 9000 secs which means a connection to a MongoDB instance through Netscaler is open for 2.5 hours. I have set it to 20 secs. I am not looking for someone to blame but probably it's our sys admin.
Wouldn't any database give you plain bad performance if settings were badly configured? I understand it was merely one of the reasons, but sometimes all you need is one.
- TheSmoke 15y agothis was a reason specific to our stupidity. why on earth would someone keep connections open for 2.5 hours? how he misses this setting? my point in this is, if you have something that balance connections between servers, check if it kills them or not.
- hieronymusN 15y agoWere you doing any connection pooling with Mongo? I'm curious what driver you were using, etc.
- alexchamberlain 15y agoHe gives the impression in the article that it was PHP.
- mnutt 15y agoPerhaps it was just some mismatch between the expectation (pooled, long-running connections) and reality. (many, many short-lived connections) I think another takeaway from this is any time you need to adjust the ulimit, take a step back and ask "Does this make sense? Is my use case exceptional enough that it won't perform within the default limits set by my OS?"