You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mysql-shun_recovery_time_sec has a nice notice of:
Note that if ProxySQL isn’t handling client traffic, there is no actual hard guarantee of the exact timing, but in practice it shouldn’t exceed this value by more than a couple of seconds.
I believe that a couple of seconds is weird but acceptable, although I'm afraid in reality there are cases in which it could be extremely long.
ProxySQL version: 2.2.0-percona-1.1, running on RHEL7. Steps to reproduce:
Create two hostgroups with some instances. It's important one node (let's call it X), is added to the both host groups.
Add some latency to the X node, for instance
tc qdisc add dev enp0s8 root netem delay 10001ms
After the node is shunned, remove the latency.
The node will remain as shunned forever. It will be correctly set to ONLINE after any client will reach a host group.
The text was updated successfully, but these errors were encountered:
Hello,
mysql-shun_recovery_time_sec
has a nice notice of:I believe that a couple of seconds is weird but acceptable, although I'm afraid in reality there are cases in which it could be extremely long.
ProxySQL version:
2.2.0-percona-1.1
, running on RHEL7. Steps to reproduce:The node will remain as shunned forever. It will be correctly set to ONLINE after any client will reach a host group.
The text was updated successfully, but these errors were encountered: