We have a situation that I was wondering if anyone had an answer to. We have a situation where we have multiple mysql boxes being used in random order for load balancing and fault tolerance. Basically the app chooses one of the machines at random, and if it can't get a connection, it tries another.
Here is the situation that happens to us. When we bring one mysql down, no big deal, any request that would have been destined for that machine goes to another machine. This part works well. The problem occurs when we start up mysql. Mysql binds to the port, then it takes about 15 seconds for innodb to startup and get ready to start serving requests. Problem is that in this 15 seconds a few hundred connections have queued up to mysql. When innodb is ready to start serving data, all of these query's hit the base and we have a backlog of requests to serve. This normally takes quite a bit of time before it is able to recover. My question is this. Is there a way to have innodb get ready and do everything it needs to do to serve data before mysql binds to the port? This way until the base is ready to serve requests, incoming clients cannot get a connection. Thanks... --shak -- Shakeel Sorathia Systems Administrator (213) 739-5348 --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
