Cluster Configuration For Runtime Components

This section explains the configuration to setup the cluster properties. A cluster defines the machines running the Core Engines, Global Throttle Manager, Cache Agent and Cache Cleanup Agents. You must define all runtime components in the same cluster except the Central Logger component. The Central Logger instance must be deployed in a separate cluster.

Configuration Files

The cluster properties are defined in the asg_core.cdd and asg_cl.cdd files.

Note:
  • All the runtime components (Core Engine, Global Throttle Manager, Cache Agent and Cache Cleanup Agent) must run in one cluster.
  • The Central Logger instance must run in a separate cluster.

To define the machines in a cluster, you must set the discover URL for the cluster.

Discover URL

The discover URL specifies how the Core Engine (node) listens for discovery requests from nodes attempting to join the cluster. When a cluster starts up, and also when new members join a cluster, a discovery process enables the members to discover each other. The discover URL specifies how an Core Engine (node) listens for discovery requests from nodes attempting to join the cluster.

The discovery URL for well-known address configuration uses the following format: 

   tcp://machine1_ipaddress:port;machine2_ipaddress:port;machine3_ipaddress:port/

where machine1, machine2, machine3 belong to same cluster.

Note: For each machine in the cluster, the discover URL must have the IP addresses of the machines with respective ports which belong to the same cluster. These machines in the cluster run the components (Core Engine, Cache Agent, Global Throttle Manager, Cache Cleanup Agent).