Skip to content

Conversation

@carlcsaposs-canonical
Copy link
Contributor

Fixes canonical/mysql-router-k8s-operator#393

@carlcsaposs-canonical
Copy link
Contributor Author

Opened canonical/mysql-router-operators#20 to improve timeout handling/logging in follow-up PR

Copy link
Collaborator

@paulomach paulomach left a 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

Copy link

@shayancanonical shayancanonical left a 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

@carlcsaposs-canonical carlcsaposs-canonical merged commit bde73cc into main Feb 18, 2025
33 of 34 checks passed
@carlcsaposs-canonical carlcsaposs-canonical deleted the add-timeout branch February 18, 2025 15:35
carlcsaposs-canonical added a commit to canonical/mysql-router-operator that referenced this pull request Feb 18, 2025
Companion PR to canonical/mysql-router-k8s-operator#394

Use 30 seconds instead of 15 since we aren't constrainted by Kubernetes pod `terminationGracePeriodSeconds`
carlcsaposs-canonical added a commit to canonical/mysql-router-operator that referenced this pull request Feb 19, 2025
Companion PR to
canonical/mysql-router-k8s-operator#394

Use 30 seconds instead of 15 since we aren't constrainted by Kubernetes
pod `terminationGracePeriodSeconds`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working as expected

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stuck at "Creating database"

6 participants