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.

Sign up for GitHub

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

Jump to bottom

Automatic tune of mysql-shun_recovery_time_sec and mysql-connect_timeout_server_max #530

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

Automatic tune of mysql-shun_recovery_time_sec and mysql-connect_timeout_server_max #530

renecannao opened this issue Apr 12, 2016 · 0 comments
Assignees
@renecannao
Labels
ADMIN CONNECTION POOL MONITOR MYSQL PROTOCOL ROUTING
Milestone
Truls

Comments

@renecannao
Copy link
Contributor

To improve reliability, mysql-shun_recovery_time_sec * 1000 should always be less than mysql-connect_timeout_server_max , in order to prevent that a server is taken out for so long that an error is returned to the client.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@renecannao renecannao

Labels
ADMIN CONNECTION POOL MONITOR MYSQL PROTOCOL ROUTING
Projects
None yet
Milestone
Truls
Development

No branches or pull requests
1 participant
@renecannao