Brion Vibber wrote:
If the connection count on the ES master really is a problem (not just a symptom of a much larger problem), then that can be mitigated by closing the connections early. But I think the only reason we're seeing this come out on the ES servers is because they have the lowest number of maximum connections, so they fail first.
It's probably easier to just bump the connection limits on ES to match or exceed the core DBs. The actual activity should never be very expensive, so a sleeping connection won't hurt much.
- -- brion
Wouldn't that mean that on next failure, core dbs will fail before external storage and the whole site will be unavailable instead of just read-only?