Bug #99701 | mysql_router return Too many connection errors | ||
---|---|---|---|
Submitted: | 27 May 2020 3:01 | Modified: | 28 May 2020 16:36 |
Reporter: | pc leon | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Router | Severity: | S2 (Serious) |
Version: | 8.0.20 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[27 May 2020 3:01]
pc leon
[27 May 2020 9:00]
MySQL Verification Team
Hi, How is your router configured? all best Bogdan
[27 May 2020 9:49]
pc leon
# File automatically generated during MySQL Router bootstrap [DEFAULT] logging_folder=/data/cluster/log runtime_folder=/data/cluster/run data_folder=/data/cluster/data keyring_path=/data/cluster/data/keyring master_key_path=/data/cluster/mysqlrouter.key connect_timeout=15 read_timeout=30 dynamic_state=/data/cluster/data/state.json [logger] level = INFO [metadata_cache:cluster] cluster_type=gr router_id=1 user=mysql_router1_l34q8b02u3bq metadata_cluster=cluster ttl=0.5 auth_cache_ttl=-1 auth_cache_refresh_interval=2 use_gr_notifications=0 [routing:cluster_rw] bind_address=0.0.0.0 bind_port=6446 destinations=metadata-cache://cluster/?role=PRIMARY routing_strategy=first-available protocol=classic [routing:cluster_ro] bind_address=0.0.0.0 bind_port=6447 destinations=metadata-cache://cluster/?role=SECONDARY routing_strategy=round-robin-with-fallback protocol=classic [routing:cluster_x_rw] bind_address=0.0.0.0 bind_port=64460 destinations=metadata-cache://cluster/?role=PRIMARY routing_strategy=first-available protocol=x [routing:cluster_x_ro] bind_address=0.0.0.0 bind_port=64470 destinations=metadata-cache://cluster/?role=SECONDARY routing_strategy=round-robin-with-fallback protocol=x i generate it by using bootstrap
[27 May 2020 9:55]
pc leon
i check the doc again , found max_connect_errors params default 100 and the doc said "If a connection from a host is established successfully within fewer than max_connect_errors attempts after a previous connection was interrupted, the error count for the host is cleared to zero. However, once a host is blocked, flushing the host cache is the only way to unblock it. To flush the host cache, execute a FLUSH HOSTS statement, a TRUNCATE TABLE statement that truncates the Performance Schema host_cache table, or a mysqladmin flush-hosts command.“ so i should flush the host cache, but how to flush hosts in mysql_router? i can't connect on it , or i should do this on primary_node?
[28 May 2020 16:36]
MySQL Verification Team
Hi, You need to connect from "non-blocked" host in order to flush hosts. all best Bogdan