...
mule.cluster.nodes=192.168.10.21,192.168.10.22,192.168.10.23
mule.cluster.multicastenabled=false
mule.clusterId=<Cluster_ID>
mule.clusterNodeId=<Cluster_Node_ID>
...
Creating and Managing a Cluster Manually
Mule Runtime Engine versions 3.5, 3.6, and 3.7 reached End of Life on or before January 25, 2020. For more information, contact your Customer Success Manager to determine how you can migrate to the latest Mule version. |
Enterprise Edition
There are 3 ways to create and manage clusters:
-
Using the Mule Management Console’s graphical interface
-
Using Runtime Manager - for more information, see Creating and Managing Clusters
-
Manually, using a configuration file
This page describes manual creation and configuration of a cluster. If you want to create and manage a cluster using the Management Console’s graphical interface, see Creating or Disbanding a Cluster.
Do not attempt mixed management of clusters If you create a cluster manually, do not attempt to manage it via the Management Console. The Management Console cannot recognize your manually-created cluster, and overwrites your cluster configuration. |
All nodes in a cluster must have the same agent version. |
Creating a Cluster Manually
Follow this procedure to create a cluster manually, using a configuration file.
-
Ensure that the node is not running, that is that the Mule Runtime Server is stopped.
-
Create a file named
mule-cluster.properties
inside the node’s$MULE_HOME/.mule
directory. -
Edit the file with parameter = value pairs, one per line. See the example below.
Note:
mule.clusterId
andmule.clusterNodeId
must be in the properties file. -
Repeat this procedure for all Mule servers that you want to be in the cluster.
-
Start the Mule servers in the nodes.
For the full list of available parameters, see Cluster Configuration Parameters.
Managing a Cluster Manually
Manual management of a cluster is only possible for clusters that have been manually created, which are not managed by the Mule Management Console.
To manually change the configuration of a cluster node, follow these steps:
-
Stop the node’s Mule ESB server.
-
Edit the node’s
mule-cluster.properties
as desired, then save the file. -
Restart the node’s Mule ESB server.
Ensure consistency across nodes Ensure that the options you apply in the configuration file are valid for all cluster nodes. Failure to do so can cause you to break the cluster configuration and inadvertently disable the cluster. |
Cluster Configuration Parameters
The following table lists the parameters of the mule-cluster.properties
file.
Property name | Description |
---|---|
|
Mandatory. Unique identifier for the cluster. It can be any alphanumeric string. |
|
Mandatory. Unique ID of the node within the cluster. It can be any integer between 1 and the number of nodes in the cluster. |
|
Comma-separated list of interfaces to use by Hazelcast. Wildcards are supported, as shown below. 192.168.1.*,192.168.100.25 |
|
The nodes that belong to the cluster, in the form The port number is optional; if not set, the default is 5701. To include more than one host, create a comma-separated list. This option configures the cluster with the specified fixed IP addresses. Use this option if you are not relying on multicast for cluster node discovery. If using this option, set Examples: Two nodes listening on port 9000: 172.16.9.24:9000,172.16.9.51:9000 Two nodes listening on port 5701: 192.168.1.19,192.168.1.20 |
|
(Boolean) Enable/disable multicast. Set to |
|
Multicast group IP address to use. |
|
Multicast port number to use. |
See Also
-
Learn about deploying and monitoring clusters.