Move to Enterprise Edition from Community Edition
With Enterprise Edition, you can benefit from additional and extended features, patch releases, Hazelcast Support, and more connectors. If you are using the Open Source Edition and want to upgrade to Enterprise, you can do this with clusters of the same version from 5.5.
The Community Edition Edition does not include the following, which are included with an Enterprise license:
-
Long term support (LTS) releases and short term support (STS) releases. For more information on LTS and STS releases, see Long-term Support Releases
-
Data Migration Tool. For more information on the Data Migration Tool, see Using the Data Migration Tool
-
Patch releases, including those for security vulnerabilities from March 2024
-
Hazelcast Support with defined SLAs. For more information on the benefits of Hazelcast Support, see Getting Support
| To use the following Enterprise Edition features they might need to be enabled on your Enterprise Edition license, and must be configured after all members have been moved to Enterprise Edition. For further information on the license requirements and configuration, see the linked documentation for the specific feature. |
-
Security persistence. For more information on storing sensitive data on disk, see Security Hardening Recommendations
-
CP Subsystem. For more information on building a strongly consistent layer for a set of distributed data structures that withstands server and client failures, see CP Subsystem
-
High-Density Memory Store (HD Memory). For more information on Hazelcast’s in-memory storage solution, which supports predictable application scaling and improved performance while minimizing pauses caused by garbage collection, see High-Density Memory Store
-
WAN Replication. For more information on synchronizing the state of multiple Hazelcast clusters across a WAN, see WAN Replication
-
Rolling upgrades. For more information on upgrading the members of a cluster without downtime, see Rolling Upgrades
-
Thread-Per-Core (TPC). For more information on improving the system performance by using one thread for networking, storage, and compute on each CPU, see Thread-Per-Core (TPC)
-
User Code Namespaces. For more information on using a container for Java classpath resources, such as user code and accompanying artifacts, see User Code Namespaces
-
Helm charts, with the exception of Commmunity-driven Open Source Helm Charts. For more information on using the Helm package manager for Kubernetes with Hazelcast, see Deploying on Kubernetes
-
Updates to connectors available before version 5.4
-
Any connectors added after version 5.4
For more information on Connectors, see Connector Guides.
In addition, if you are using our tools, Community Edition does not include the following:
-
Hazelcast Operator to support your Kubernetes deployments. For more information on Operator, refer to the Hazelcast Operator documentation
-
Client filtering, Prometheus Exporter, Config Health Check, clustered REST, or JMX support in Hazelcast Management Center
Management Center also disables with clusters of more than three members.
For more information on Management Center, refer to the Management Center documentation.
High-level Process
To upgrade your Community Edition cluster to an Enterprise Edition cluster of the same version, you can use a rolling restart.
The rolling restart supports the IMap, ReplicatedMap, and Topic data structures.
For each member in the Community Edition cluster, the rolling restart process is as follows:
-
Shut down the member and wait for all partitions to migrate to the rest of the cluster
-
Upgrade the member’s codebase
-
Restart the member
You must not configure the Enterprise Edition features that you want to use until all members have been successfully moved from Community Edition to Enterprise Edition.
For further information on rolling restarts, see Upgrade Cluster to Enterprise Edition.
