Hazelcast IMDG 3.8
- Standard Support for IMDG 3.8 ended in February 2019.
- Extended Support will continue for an additional 18 months.
For more information see the full list of Version Support Windows.
Maven Repo URL Change
Latest News / Releases
Hazelcast IMDG 3.11.2 BETA-2
Hazelcast IMDG Enterprise New Features
- Blue-Green and Disaster Recovery for Java Clients:Introduced the support for Hazelcast Java clients to switch between alternate clusters. See the Blue Green and Disaster Recovery section.
Hazelcast IMDG Open Source New Features
- CP Subsystem: Implementing the Raft consensus algorithm, Hazelcast introduces its CP subsystem which runs within a Hazelcast cluster and offers linearizable implementations of Hazelcast’s concurrency APIs. See the CP Subsystem chapter.
- Querying JSON Strings: You can now query JSON strings stored inside your Hazelcast clusters. See the Querying JSON sections.
- Pipelining: Introduced pipelining mechanism which can be used to send multiple requests in parallel to Hazelcast members or clients, and to read the responses in a single step. See the Pipelining Section.
- Support for Multiple Endpoints When Configuring Member’s Networking: Added the ability to configure the Hazelcast members with separate server sockets for different protocols. See the Advanced Network configuration section.
- YAML Configuration Support: Added the support for configuring Hazelcast in YAML. See the Configuring Declaratively with YAML section.
Hazelcast IMDG Enterprise Enhancements
- Sharing Hot Restart base-dir among Multiple Members: The base directory for the Hot Restart feature ("base-dir") is now used as a shared directory between multiple members, and each member uses a unique sub-directory inside this base directory. This allows members to use the same configuration on all the members. Previously, each member had to use a separate directory which complicated the deployments on cloud-like environments. During the restart, a member tries to lock an already existing Hot Restart directory inside the base directory. If it cannot acquire any, then it creates a fresh new directory. See the Configuring Hot Restart section.
- Lower Latencies and Higher Throughput in WAN Replication: Improved the design of the WAN replication mechanism to allow configuring it for lower latencies and higher throughput. See the Tuning WAN Replication For Lower Latencies and Higher Throughput section.
- Add/Remove WAN Publishers in a Running Cluster:Introduced the ability to dynamically add or remove WAN publishers (target clusters). See the Dynamically Adding WAN Publishers section.
- Automatic Removal of Stale Hot Restart Data: Introduced an option that allows the stale Hot Restart data to be removed automatically. See the description of the "auto-remove-stale-data" configuration element in the Configuring Hot Restart section.
- Client Permission Handling When a New Member Joins:Introduced the "on-join-operation" declarative configuration attribute for the client permission in the Security configuration (its programmatic configuration equivalent is setOnJoinPermissionOperation() method). This attribute allows you to choose whether a new member joining to a cluster will apply the client permissions stored in its own configuration, or will use the ones defined in the cluster. See the Handling Permissions When a New Member Joins section. Note that this feature is also implemented in the Hazelcast IMDG 3.11.2 release; but, instead of a configuration attribute, you can use a system property specific for that release. See the "Enhancements" section under Hazelcast IMDG 3.11.2 notes below.
- Automatic Cluster Version Change after a Rolling Upgrade:Introduced the ability to automatically upgrade the cluster version after a rolling upgrade. See the Upgrading Cluster Version section.
- FIPS 140-2 Validation: Hazelcast now can be configured to use a FIPS 140-2 validated module. See the FIPS 140-2 section.
Hazelcast IMDG Open Source Enhancements
- Client Instance Names and Labels: You can now retrieve the names of client instances on the member side. Moreover, client labels have been introduced so that you can group your clients and/or perform special operations for specific clients. See the Defining Client Labels section.
- Composite Indexes: Introduced the ability to recognize the queries that use all the indexed properties and treat them as a composite, e.g., foo = 1 and bar = 2 and foobar = 3. See the Composite Indexes section.
- REST Endpoint Groups: With this enhancement you can enable or disable:
⇒ REST API completely
⇒ Memcache protocol
⇒ REST endpoint groups. See the Using the REST Endpoint Groups section.
- Support for JDK 6 and 7 has been dropped. The minimum Java version that Hazelcast supports now is Java 8. See the Supported JVMs section.
Hazelcast IMDG 3.11.2
- Introduced a new system property ("hazelcast.security.permissions.operation.on-join") that allows you to choose whether a new member joining to a cluster will apply the client permissions stored in its own configuration, or will use the ones defined in the cluster. See the Handling Permissions When a New Member Joins section.
- If you have multiple Hazelcast members on a single machine and you are using unisocket clients, we recommend that you set explicit ports for each member. Then you should provide those ports in your client configuration when you give the member addresses. Otherwise, all the load coming from your clients may go through a single member.
Management Center 3.12-ALPHA-1
- New Management Center Configuration Tool ("mc-conf") which allows you to update certain parts of the MC configuration, including creating users externally from the command line.
- The fields of the notifications in the WAN Sync page are now searchable.
- Improved the look and feel behavior of the Scripting and Time Travel pages.
- The process for shutting down a member, now, does not require the group password.
Kubernetes Cloud Discovery 1.4
- Hazelcast ZONE_AWARE for Kubernetes clusters deployed on multiple zones.
- Hazelcast Public IP resolution to enable external Smart Client.
- Introduced the ability to discover all Hazelcast PODs by default instead of all PODs that have services assigned (change the usage of Kubernetes API to call /pods instead of /endpoints).
- Add the "ca-certificate" property to allow the complete authentication for external clients.
- "Changed the scope of the Hazelcast dependency in "pom.xml": starting with this release, you need to define the Hazelcast dependency separately for "hazelcast-kubernetes".
AWS Cloud Discovery 2.4
- Changed the scope of the Hazelcast dependency in "pom.xml".
Google Cloud Platform Discovery 1.1.1
Azure Cloud Discovery 1.2.2
- Updated Azure SDK version to 1.14
- Changed the scope of the Hazelcast dependency in "pom.xml": starting with this release, you need to define the Hazelcast dependency separately for "hazelcast-azure".
Hazelcast Eureka Discovery 1.1.1
Second Level Cache for Hibernate5 1.3.2
Second Level Cache for Hibernate 3.8.4
Hazelcast DynaCache Plugin 0.3
- HazelcastClientOSGiService was moved to this module and dependencies were updated. There's no need for a special branch of Hazelcast client to be used with OSGi anymore.
Best wishes from the Hazelcast Team!
–The Hazelcast Team