4.2.x to 4.3.x Migration Guide
This is a minor HiveMQ upgrade. HiveMQ 4.3 is a drop in replacement for HiveMQ 4.2.x
Create a backup of the entire HiveMQ 4.2.x installation folder from which you want to migrate
Install HiveMQ 4.3 as described in the HiveMQ Installation Guide
Migrate the contents of the configuration file from your old HiveMQ 4.2.x installation
To migrate your persistent data, copy everything from the
datafolder of your backup to the data folder of the new HiveMQ 4.3 installation. The first time you start HiveMQ 4.3, the file storage formats of the persistent data from your previous installation are automatically updated in the new persistent storage.
You can upgrade from HiveMQ 4.2.x to HiveMQ 4.3 without making changes to your configuration file.
When you migrate, HiveMQ 4.3 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.2.x installation to the data folder of your new HiveMQ 4.3 installation.
cp -r /opt/hivemq-4.2.2/data/* /opt/hivemq-4.3.0/data/
The first time you start HiveMQ 4.3, the file storage formats of the persistent data from your previous installation are automatically updated in the new persistent storage.
Rolling upgrades are supported and it is possible to run HiveMQ version 4.2 and version 4.3 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 Clustering Documentation.
Since version 4.3, HiveMQ only allows MQTT clients to connect if a security extension is present.
For testing purposes, HiveMQ includes a
hivemq-allow-all-extension that authorizes all MQTT clients to connect to HiveMQ.
Before you use HiveMQ in production, you must add an appropriate security extension and remove the
You can download security extensions from the HiveMQ Marketplace
or develop your own security extension.
HiveMQ 4.3 uses less JVM heap than HiveMQ 4.2. However, the overall RAM usage of the HiveMQ 4.3 processes is roughly the same. We recommended that you configure the JVM heap with 50% of the RAM that is available on the system on which you run HiveMQ. More information on how to configure the heap is available here.
|HiveMQ 4.3 requires Glibc version 2.12 or higher.
The HiveMQ 4.3 Control Center offers new insights into your MQTT deployment. If you use the HiveMQ Enterprise Security Extension to restrict access to your control center and you want privileged users to access the new control center features, you must grant new permissions to these users.
You can grant any or all of these new permissions to the appropriate users or roles as desired.
Allows the user to view the retained message details.
Allows the user to see user properties of messages.
Lack of this permission hides the user properties on all pages.