Revision 156/136

_{Thursday, July 4, 2024}

Dear community,

We are glad to report that we have just released a new updated version for Charmed ZooKeeper on the 3/stable channel, upgrading its revision from 126 to 136. The release of a new version was promoted by the need of backporting some features that should provide increased robustness and resilience during operation as well as smaller workload upgrades and fixes. See the technical notes for further information.

Please reach out should you have any question, comment, feedback or information. You can find us here in Matrix or also on Discourse.

Features

• [DPE-3726] Workload upgrade to 3.8.4-ubuntu0

Bugfixes

• [DPE-4183] (backport) fix: only handle quorum removal on relation-departed
• [DPE-4362] (backport) add alive check fix

Canonical Data issues are now public on both Jira and GitHub platforms.

GitHub Releases provide a detailed list of bugfixes, PRs, and commits for each revision.

Inside the charms

• Charmed ZooKeeper charm ships the ZooKeeper 3.8.4-ubuntu0, built and supported by Canonical
• Charmed Kafka charm ships the Kafka 3.6.0-ubuntu0, built and supported by Canonical
• Charmed ZooKeeper charm is based on charmed-zookeeper snap on the 3/stable (Ubuntu LTS “22.04” - core22-based)
• Charmed Kafka charm is based on charmed-kafka snap on the 3/stable channel (Ubuntu LTS “22.04” - core22-based)
• Principal charms supports the latest LTS series “22.04” only.

More information about the artifacts are provided by the following table:

Technical notes

• Rev126 on Charmed ZooKeeper was observed to sporadically trigger ZooKeeper reconfiguration of the clusters by removing all server but the Juju leader from the ZooKeeper quorum. This leads to a non-highly available cluster, that it is however still up and running. The reconfiguration generally resulted from some glitch and connection drop with the Juju controller that resulted in transient inconsistent databag of juju events. This was once observed during a controller upgrade (see reported bug on Juju), but its occurrence is not limited to it. The current revision provides more robust logic (ticket DPE-4183) to avoid dynamic reconfiguration in such cases.
• Upgrades from previous stable versions can be done with the standard upgrading process, as outlined in the documentation