4.23.x to 4.24.x Migration Guide

This is a minor HiveMQ upgrade. HiveMQ 4.24 is a drop in replacement for HiveMQ 4.23.x.

You can learn more about all the new features HiveMQ 4.24 introduces in our release blogpost.

HiveMQ is prepackaged with all HiveMQ Enterprise Extensions (disabled), HiveMQ Data Hub, the open-source MQTT CLI tool, and the HiveMQ Swarm load-testing tool (MQTT CLI and HiveMQ Swarm are located in the tools folder of your HiveMQ installation).

Starting with the HiveMQ 4.9 LTS release, HiveMQ provides enhanced version compatibility for all HiveMQ releases.
For more information, see HiveMQ Rolling Upgrade Policy and our Introducing Flexible MQTT Platform Upgrades with HiveMQ blog post.

When you migrate from one HiveMQ version to another, review the upgrade information for each version between your current HiveMQ version and the target HiveMQ version.
Note changes that are relevant to your use case and adjust your configuration as needed.

Upgrade a HiveMQ Cluster

Rolling upgrades are supported, and it is possible to run HiveMQ version 4.23 and version 4.24 simultaneously in the same cluster. By default, the HiveMQ cluster enables all new cluster features when all nodes are upgraded to the new version. No manual intervention is required.

Please follow the instructions in our user guide to ensure a seamless and successful rolling upgrade.

For more information, see HiveMQ Clusters.

Upgrade a Single-node HiveMQ Instance

  • Create a backup of the entire HiveMQ 4.23.x installation folder from which you want to migrate.

  • Install HiveMQ 4.24 as described in the HiveMQ Installation Guide.

  • Migrate the contents of the configuration file from your old HiveMQ 4.23.x installation.

  • To migrate your persistent data, copy everything from the data folder of your backup to the data folder of the new HiveMQ 4.24 installation.

HiveMQ 4.24 adds multiple cluster stability and performance improvements for machines with more than 16 virtual CPUs. For high-load scenarios that have historically exhibited elevated mean CPU usage levels of 70-80%, these changes can result in higher CPU usage. However, HiveMQ 4.24 compensates for any higher CPU usage with lower end-to-end PUBLISH message latencies and smaller subscriber client queue sizes.

Configuration File Changes

HiveMQ prevents the startup if your configuration file contains invalid values. For more information, see Configuration Validation.

Persistent Data Migration

When you migrate, HiveMQ 4.24 automatically updates the file storage formats of all the data that you copied into your new data folder.

To migrate the persistent data, you must copy everything in the data folder of the previous HiveMQ 4.23.x installation to the data folder of your new HiveMQ 4.24 installation.

Linux example
cp -r /opt/hivemq-4.23.0/data/* /opt/hivemq-4.24.0/data/

The first time you start HiveMQ 4.24, the file storage formats of the persistent data from your previous installation are automatically updated in the new persistent storage.