On 06/12/2014 05:08 PM, Sergei Golubchik wrote:
Hi, Honza!
there are apparently some tools out there [1], that check if the server
is up quite often, while not closing the connection properly. It
eventually ends in 'many connection errors', because max_connect_errors
is always limited now.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1104957
What's the status of that?
Was any workaround (skip-name-resolve, max_connect_errors=4294967295 or
FLUSH HOSTS, which can be run periodically with CREATE EVENT) considered
good enough? I see that the bug is closed as NOTABUG.
Guys who reported this started using skip-name-resolve=1, but it does
more than necessary, so it is still considered a work-around and it
still seems to be a good idea to add some feature that would disable
only max_connect_errors.
Honza
_______________________________________________
Mailing list: https://launchpad.net/~maria-developers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~maria-developers
More help : https://help.launchpad.net/ListHelp
