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

Refactor scale down on units to use teardown events #82

Closed
shayancanonical opened this issue Jul 19, 2022 · 2 comments
Closed

Refactor scale down on units to use teardown events #82

shayancanonical opened this issue Jul 19, 2022 · 2 comments

Comments

@shayancanonical
Copy link
Contributor

There is currently a juju bug where teardown events are not fired when a unit is scaling down. This prevents the departing unit from removing itself from the cluster using mysqlsh.remove_instance(self).

Since the unit departs before it can remove itself from the cluster, the juju leader unit has to use mysqlsh.remove_instance(departed_unit, {force: true}) to remove the already departed unit. Furthermore, if there is a loss of quorum, the charm uses mysqlsh.force_quorum_using_partition_of(first_online_unit). This is not the ideal solution, and this issue has been created to keep track of the juju bug resolution and replace the scale down logic to use teardown events when they are firing.

@taurus-forever
Copy link
Contributor

@shayancanonical can you please re-check this on pre-2.9.43 with fixed scale-down K8s logic. Tnx!

@paulomach
Copy link
Contributor

Closed on #249

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

3 participants