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

[Feature] Enhanced upgrades tailored for MariaDB reliability. #321

Closed
mariadb-mmontes opened this issue Jan 2, 2024 · 1 comment · Fixed by #635
Closed

[Feature] Enhanced upgrades tailored for MariaDB reliability. #321

mariadb-mmontes opened this issue Jan 2, 2024 · 1 comment · Fixed by #635
Assignees
@mmontes11
Labels
feature priority-short-term To be resolved in the short term

Comments

@mariadb-mmontes
Copy link
Contributor

mariadb-mmontes commented Jan 2, 2024 •
edited by mmontes11
Loading

Describe the solution you'd like
We should implement a custom, reliable, MariaDB state aware upgrade mechanism:

  • Restart replicas and then master
  • Restart one Pod at a time making sure it is in sync.

Describe alternatives you've considered
Use default StatefulSet rolling upgrade strategies, but it doesn't take into account the MariaDB state, which means that a master node could potentially be upgraded first, and therefore also disrupted.

Additional context
This will unblock spec.myCnf updates:
@mmontes11 mmontes11 mentioned this issue Jan 2, 2024
Closed
1 task
@mmontes11 mmontes11 changed the title [Feature] Custom upgrades: Upgrade replicas first [Feature] Custom, reliable and MariaDB aware upgrades Mar 8, 2024
@mmontes11 mmontes11 changed the title [Feature] Custom, reliable and MariaDB aware upgrades [Feature] Enhanced upgrades tailored for MariaDB reliability. Mar 8, 2024
@mmontes11 mmontes11 added the priority-short-term To be resolved in the short term label Mar 13, 2024
@mmontes11 mmontes11 added priority-mid-term To be resolved in the mid term and removed priority-short-term To be resolved in the short term labels Mar 25, 2024
@mariadb-pieterhumphrey
Copy link
Collaborator

Doesn't use K8s stateful set construct.

Also implies feature flagging "upgradable" as a pod level attribute, so you can opt replicas/masters in/out of the upgrade path.
Enables TLS: #137

Reminder: In Galera, all nodes are masters / all writable. In async replication, replicas cannot receive writes so they need a different upgrade path.

@mmontes11 mmontes11 mentioned this issue May 14, 2024
Closed
@mmontes11 mmontes11 added priority-short-term To be resolved in the short term and removed priority-mid-term To be resolved in the mid term labels May 21, 2024
@mmontes11 mmontes11 pinned this issue May 21, 2024
@mmontes11 mmontes11 mentioned this issue May 21, 2024
Merged
@mmontes11 mmontes11 unpinned this issue May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mmontes11 mmontes11

Labels
feature priority-short-term To be resolved in the short term
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support for ReplicasFirstPrimaryLast update strategy mariadb-operator/mariadb-operator
3 participants
@mmontes11 @mariadb-pieterhumphrey @mariadb-mmontes