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

Automatic tune mysql-shun_recovery_time_sec if only 1 backend was available #531

Closed
renecannao opened this issue Apr 12, 2016 · 0 comments
Closed

Comments

@renecannao
Copy link
Contributor

To improve reliability, mysql-shun_recovery_time_sec should self tune when there is only 1 server in a hostgroup .

@renecannao renecannao self-assigned this Apr 12, 2016
@renecannao renecannao added this to the Truls milestone Apr 12, 2016
renecannao added a commit that referenced this issue Apr 12, 2016
See issues #530 and #531

Closes #530
Closes #531
renecannao added a commit that referenced this issue May 11, 2016
Fix issue #566
Regression introducted in #531
jhriggs added a commit to jhriggs/proxysql that referenced this issue Aug 25, 2020
Issue sysown#531 added "a desperate attempt to bring back online any shunned server" when no servers are available; however, no indication or notification of this is logged. Add a log message indicating that the hostgroup has no servers available and shunned hosts are being checked before the normal shun recovery time.
renecannao pushed a commit that referenced this issue Sep 8, 2020
Issue #531 added "a desperate attempt to bring back online any shunned server" when no servers are available; however, no indication or notification of this is logged. Add a log message indicating that the hostgroup has no servers available and shunned hosts are being checked before the normal shun recovery time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant