Description:
performance_schema.host_cache provides some useful information on a host, including errors. However, I don't see a reference to the aborted_client errors for that host which would be most interesting.
How to repeat:
user@myhost-5-6 [performance_schema]> select * from host_cache where ip = '1.2.3.4'\G
*************************** 1. row ***************************
IP: 1.2.3.4
HOST: NULL
HOST_VALIDATED: YES
SUM_CONNECT_ERRORS: 0
COUNT_HOST_BLOCKED_ERRORS: 0
COUNT_NAMEINFO_TRANSIENT_ERRORS: 0
COUNT_NAMEINFO_PERMANENT_ERRORS: 1
COUNT_FORMAT_ERRORS: 0
COUNT_ADDRINFO_TRANSIENT_ERRORS: 0
COUNT_ADDRINFO_PERMANENT_ERRORS: 0
COUNT_FCRDNS_ERRORS: 0
COUNT_HOST_ACL_ERRORS: 0
COUNT_NO_AUTH_PLUGIN_ERRORS: 0
COUNT_AUTH_PLUGIN_ERRORS: 0
COUNT_HANDSHAKE_ERRORS: 0
COUNT_PROXY_USER_ERRORS: 0
COUNT_PROXY_USER_ACL_ERRORS: 0
COUNT_AUTHENTICATION_ERRORS: 0
COUNT_SSL_ERRORS: 0
COUNT_MAX_USER_CONNECTIONS_ERRORS: 0
COUNT_MAX_USER_CONNECTIONS_PER_HOUR_ERRORS: 0
COUNT_DEFAULT_DATABASE_ERRORS: 0
COUNT_INIT_CONNECT_ERRORS: 0
COUNT_LOCAL_ERRORS: 0
COUNT_UNKNOWN_ERRORS: 0
FIRST_SEEN: 2014-07-25 00:22:22
LAST_SEEN: 2015-03-20 08:33:42
FIRST_ERROR_SEEN: 2014-07-25 00:22:22
LAST_ERROR_SEEN: 2014-07-25 00:22:22
1 row in set (0.00 sec)
user@myhost-5-6 [performance_schema]>
Suggested fix:
Adding a column COUNT_ABORTED_CLIENT_ERRORS would be good.
See: http://dev.mysql.com/doc/refman/5.6/en/server-status-variables.html#statvar_Aborted_client...
as this would help identify issues with a particular host etc.
This can't be added to 5.6 due to the change adusting a base table definition.
So perhaps if there's time it would be good to go into 5.7?
Description: performance_schema.host_cache provides some useful information on a host, including errors. However, I don't see a reference to the aborted_client errors for that host which would be most interesting. How to repeat: user@myhost-5-6 [performance_schema]> select * from host_cache where ip = '1.2.3.4'\G *************************** 1. row *************************** IP: 1.2.3.4 HOST: NULL HOST_VALIDATED: YES SUM_CONNECT_ERRORS: 0 COUNT_HOST_BLOCKED_ERRORS: 0 COUNT_NAMEINFO_TRANSIENT_ERRORS: 0 COUNT_NAMEINFO_PERMANENT_ERRORS: 1 COUNT_FORMAT_ERRORS: 0 COUNT_ADDRINFO_TRANSIENT_ERRORS: 0 COUNT_ADDRINFO_PERMANENT_ERRORS: 0 COUNT_FCRDNS_ERRORS: 0 COUNT_HOST_ACL_ERRORS: 0 COUNT_NO_AUTH_PLUGIN_ERRORS: 0 COUNT_AUTH_PLUGIN_ERRORS: 0 COUNT_HANDSHAKE_ERRORS: 0 COUNT_PROXY_USER_ERRORS: 0 COUNT_PROXY_USER_ACL_ERRORS: 0 COUNT_AUTHENTICATION_ERRORS: 0 COUNT_SSL_ERRORS: 0 COUNT_MAX_USER_CONNECTIONS_ERRORS: 0 COUNT_MAX_USER_CONNECTIONS_PER_HOUR_ERRORS: 0 COUNT_DEFAULT_DATABASE_ERRORS: 0 COUNT_INIT_CONNECT_ERRORS: 0 COUNT_LOCAL_ERRORS: 0 COUNT_UNKNOWN_ERRORS: 0 FIRST_SEEN: 2014-07-25 00:22:22 LAST_SEEN: 2015-03-20 08:33:42 FIRST_ERROR_SEEN: 2014-07-25 00:22:22 LAST_ERROR_SEEN: 2014-07-25 00:22:22 1 row in set (0.00 sec) user@myhost-5-6 [performance_schema]> Suggested fix: Adding a column COUNT_ABORTED_CLIENT_ERRORS would be good. See: http://dev.mysql.com/doc/refman/5.6/en/server-status-variables.html#statvar_Aborted_client... as this would help identify issues with a particular host etc. This can't be added to 5.6 due to the change adusting a base table definition. So perhaps if there's time it would be good to go into 5.7?