Hi Paul, On Wed, Jan 13, 2010 at 12:31:09PM -0800, Paul Hirose wrote: (...) > >> as a workaround, you can disable the mysql connection_errors checking by > >> adding max_connect_errors=999999999 in you my.cnf (...)
> I don't know what the mysql-check does (sorry, haven't dug through the > actual changed commit.) I don't see any reference to it in the 1.4 > docs yet, so I figure it'll be there once 1.4 is actually done. yes the doc is there too. It's in the latest snapshot. I think we should add a warning and Hervé's suggestion above there. Hervé, care to send a patch for the doc ? > One thing I've had trouble with when doing mysql though was the > connection timeouts. I tried using tcpka but that didn't do it. it would not change because tcpka enables tcp keepalives which just the system is aware of. It is not applicative at all and generally runs at a very low rate (eg: one KA every 2 hours). > So I > do have trouble with connections of a long duration but where there is > little actual data. Usually some client application that makes a > connection once at the start and then goes idle waiting for some input > from a client of its own. If anyone might know how to keep such an > idle (but still valid) connection alive (other than a gigantic > timeout), I'd love suggestions. You have no other possibility. What you want is to maintain open a connection eventhough nothing happens at the application level for a very long period. That's what the timeout is made for. People balancing TSE farms or LDAP servers are well aware of the same requirement :-) Regards, Willy
