-
Notifications
You must be signed in to change notification settings - Fork 9
Add default 15 second timeout to pebble exec #394
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
Conversation
|
Opened canonical/mysql-router-operators#20 to improve timeout handling/logging in follow-up PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do, apparently, need to have default timeout.
Checking all queries the router does, none should take longer under normal conditions, meaning that if get stuck something went wrong and it was acknowledged.
The specific handler in the bug report is idempotent, worth checking if it's the case everywhere a timeout can happen
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would agree with Paulo that the bootstrap timeout could be set to a higher value than the default timeout
Companion PR to canonical/mysql-router-k8s-operator#394 Use 30 seconds instead of 15 since we aren't constrainted by Kubernetes pod `terminationGracePeriodSeconds`
Companion PR to canonical/mysql-router-k8s-operator#394 Use 30 seconds instead of 15 since we aren't constrainted by Kubernetes pod `terminationGracePeriodSeconds`
Fixes canonical/mysql-router-k8s-operator#393