3.3.x to 3.4.x Migration Guide
This is a minor HiveMQ upgrade. HiveMQ 3.4 is a drop in replacement for HiveMQ 3.3.x
|No manual steps are required for upgrading from HiveMQ 3.3 to HiveMQ 3.4.|
Create a backup of the entire HiveMQ installation folder
Install HiveMQ 3.4 as described in the HiveMQ Installation Guide
Migrate the configuration file contents of your old HiveMQ installation
To migrate the persistent data, copy all contents in the
datafolder from your backup to the new HiveMQ 3.4 data folder. On first start HiveMQ 3.4 will migrate the persistent data from your previous installation into its new persistent storage.
HiveMQ 3.4 introduces some changes to the configuration file for:
HiveMQ 3.4 automatically migrates all data in your data folder from previous versions to updated file storage formats.
To allow HiveMQ to migrate the persistent data from previous versions you have to copy the contents of your data folder from the previous installation to the data folder of the new installation.
cp -r /opt/hivemq-3.3.4/data/* /opt/hivemq-3.4.0/data/
On the first start up HiveMQ 3.4 will automatically migrate the persistent data from your previous installation into its new persistent storage.
Rolling upgrades are supported and it’s possible to run HiveMQ version 3.3 and version 3.4 simultaneously in the same cluster. When all nodes are upgraded to the new version, all new cluster features are enabled by default by the HiveMQ cluster. No manual intervention is needed.
Please follow the instructions in our user guide to ensure a seamless and successful rolling upgrade.
Please see the HiveMQ Clustering Documentation for more information.
HiveMQ 3.4 has JMX enabled by default at port 9010.
To run more than one HiveMQ on a single server, change the port in your startup script.
JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9010 ..."
rem set "JAVA_OPTS=-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9010 ..."
HiveMQ 3.4 comes with a cluster overload protection mechanism.
For more information see Cluster Overload Protection.