MysteryMan wrote:I'm pretty exhausted but the glitch appears to be fixed.
Here's a high level explanation of what happened:
Generally speaking, opening a connection to a sql server takes a bit of resources. Think of it as the metaphorical equivalent of wiring up and then taking down a phone line. You don't want to do that a lot.
This is where the connection pool comes in. So what happens is that you wire a small number of connections and every node shares the line. The calls are quick so no line monopolizes the server. Think of it like a building that shares a few phone lines for quick conversations.
Instead what happened is that every person in the building got a new phone line wired up whenever they wanted to talk to MySQL. This freaked out MySQL and it had a heart attack. Vadym gave it a cyborg body so it could handle the load like the bionic man, but really the solution would be to stop flooding the server.
The thing is, there shouldn't be that many lines between the web and sql - the nodes should just share a couple public lines.
On a related note, i'll be speaking at the Microsoft building later on why we left Azure.
Users browsing this forum: No registered users and 1 guest