Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mysql-shun_recovery_time_sec not reliable when there's not traffic to the host group #3649

Open
impimp opened this issue Oct 1, 2021 · 0 comments

Comments

@impimp
Copy link

impimp commented Oct 1, 2021

Hello,

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:

  1. Create two hostgroups with some instances. It's important one node (let's call it X), is added to the both host groups.
  2. Add some latency to the X node, for instance
tc qdisc add dev enp0s8 root netem delay 10001ms
  1. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant