Hi Hervé, First of all, sorry, I wanted to contact you directly to know the status of this development, but I didn't find your email. I realized too late that I saw it in the commit sooner in the morning :)
Le Mercredi 13 Janvier 2010 12:56:30, Hervé COMMOWICK a écrit : > Hi Cyril, > > I know the check is not perfect, because it doesn't handle a correct > disconnection. > Mysql expect the client to talk, and i think it's weird... in the > future, i think it will be better to do a *real* mysql ping, but at the > moment, the checks API doesn't let me handle this in a cleaner way. > > as a workaround, you can disable the mysql connection_errors checking by > adding max_connect_errors=999999999 in you my.cnf Yes I guessed you knew that, but I thought it was better to signal it for users interested by this check. Maybe this workaround should appear in the documentation, like the note about the client IP, until the handshake is complete. This would minimize the risk to discover too late that the haproxy server has been blacklisted by the mysql server (the guy who administrate haproxy is not always the one for mysql, for example). -- Cyril Bonté
