Mysql Router
- By MySQL Charm Maintainers
- Cloud
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/edge | 252 | 02 Oct 2024 | |
latest/edge | 251 | 02 Oct 2024 | |
latest/edge | 250 | 02 Oct 2024 | |
latest/edge | 249 | 02 Oct 2024 | |
latest/edge | 201 | 19 Jun 2024 | |
latest/edge | 108 | 12 Sep 2023 | |
latest/edge | 62 | 10 Feb 2023 | |
8.0/stable | 245 | 25 Sep 2024 | |
dpe/candidate | 225 | 28 Aug 2024 | |
dpe/candidate | 224 | 28 Aug 2024 | |
dpe/candidate | 223 | 28 Aug 2024 | |
dpe/beta | 225 | 23 Aug 2024 | |
dpe/beta | 224 | 23 Aug 2024 | |
dpe/beta | 223 | 23 Aug 2024 | |
dpe/edge | 248 | 30 Sep 2024 | |
dpe/edge | 247 | 30 Sep 2024 | |
dpe/edge | 246 | 30 Sep 2024 | |
8.0.19/stable | 26 | 05 May 2022 | |
8.0.19/edge | 26 | 05 May 2022 | |
8.0.19/edge | 15 | 26 Apr 2022 |
juju deploy mysql-router --channel dpe/edge
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
Minor Rollback
Example: MySQL Router 8.0.34 -> MySQL Router 8.0.33
(including simple charm revision bump: from revision 43 to revision 42)
WARNING: do NOT trigger
rollback
during the runningupgrade
action! It may cause unpredictable MySQL Cluster and/or MySQL Router state!
Minor rollback steps
The rollback is NOT necessary if sacrificial unit
is created before the upgrade, just remove it using scale-down the application. Otherwise perform the rollback:
-
Rollback. Perform the charm rollback using
juju refresh
. The unit with the maximal ordinal will be rolled-back first and rollback continues for entire application. - Check. Make sure the charm and cluster are in healthy state again.
Manual Rollback
After a juju refresh
, case there any version incompatibilities in charm revisions or it dependencies, or any other unexpected failure in the upgrade process, the upgrade process will be halted an enter a failure state.
Although the underlying MySQL Cluster and MySQL Router continue to work, it’s important to rollback the charm to previous revision so an update can be later attempted after a further inspection of the failure.
To execute a rollback we take the same procedure as the upgrade, the difference being the charm revision to upgrade to. In case of this tutorial example, one would refresh the charm back to revision 88
, the steps being:
Step 1: Rollback
When using charm from charmhub:
juju refresh mysql-router --revision=88
Case deploying from local charm file, one need to have the previous revision charm file and the mysql-image
resource, then run:
juju refresh mysql-router --path=./mysql-router_ubuntu-22.04-amd64.charm
Where mysql-router_ubuntu-22.04-amd64.charm
is the previous revision charm file.
The biggest ordinal unit will be rolled out and should rejoin the cluster after settling down. After the refresh command, the juju controller revision for the application will be back in sync with the running MySQL Router revision.
Step 2: Check
The future improvement is planned to check the state on pod/cluster on a low level. At the moment check juju status
to make sure the cluster state is OK.