maybe a null value?


2014-06-09 12:14 GMT-03:00 Honza Horak <hhorak@redhat.com>:
Hi guys,

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.

I understand that this way of checking may be wrong, but there may be scenarios where we do not want to check for `max_connect_errors` at all.

So, would it be acceptable for mariadb to change behaviour of max_connect_errors option, so that it accepts also 0 as a possible value, which would mean 'do not check connect errors at all'?

I'm bringing the idea here first, but will submit a report and possibly patch if it does not seem to be undesired behaviour.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1104957

TIA and regards,
Honza

_______________________________________________
Mailing list: https://launchpad.net/~maria-developers
Post to     : maria-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-developers
More help   : https://help.launchpad.net/ListHelp



--
Roberto Spadim
SPAEmpresarial
Eng. Automação e Controle