Installing Hazelcast
This topic describes how to configure the Hazelcast Platform.
Before you begin
Following are the supported versions.
Software | Version |
---|---|
Hazelcast |
|
Important: Hazelcast 5.3.x and later releases no longer support the IBM®
Java™ Development Kit (JDK) 8 runtime.
Procedure
- Download the Hazelcast Platform in a compressed file format from the following location.
- Extract the compressed file format to your workstation.
- Browse to the /hazelcast-x.x.x/bin folder.
- Replace the existing hazelcast.xml file with the file that you copy from the $TOP/mdmui/dynamic/hazelcast folder.
- Hazelcast 5.3.6To run Hazelcast
service, you need to manually add the following in the
/hazelcast-x.x.x/bin/hz
file.
export JAVA_HOME=<jdk11_home path>
- Use the following command to start the Hazelcast service as a background service.
-
Fix Pack 10 and later
-
nohup ./hz start &
Fix Pack 9 and earlier
-
nohup ./hz-start &
-
What to do next
You need to configure Hazelcast in the TCP/IP mode to enable discovering cluster members by
using TCP. When you configure Hazelcast to discover members by TCP/IP, you must list all or
a subset of the members' hostnames, IP addresses or both as the cluster members. You do not
have to list all of the cluster members, but at least one of the listed members must be
active in the cluster when a new member joins. To set your Hazelcast to be a full TCP/IP
cluster, set the following configuration elements:
- Set the enabled attribute of the multicast element to "false".
- Set the enabled attribute of the aws element to "false".
- Set the enabled attribute of the tcp-ip element to "true".
- Set your member elements within the tcp-ip element.
<hazelcast>
...
<network>
...
<join>
<multicast enabled="false">
</multicast>
<tcp-ip enabled="true">
<member>machine1:5702</member>
<member>machine2:5702</member>
<member>machine3:5702</member>
</tcp-ip>
...
</join>
...
</network>
...
</hazelcast>
As shown in the example, you can provide IP addresses or
hostnames for the member elements. Ensure that you provide the correct port along with the
IP address. For more details, see Discovering Members by TCP.