Cluster-specific Listeners

March 26, 2020 Contributors

This section describes the listeners that are used in a cluster configuration.

ECCluster_Listener Configuration

Any direct, point-to-point communication between cluster nodes that does not require membership-wide ordering semantics will be performed over TCP/IP via the port specified in the Listen stanza within the ECCluster_Listener scope. Any node can establish a connection to the destination node at the address specified by the ECCluster_Listener and point-to-point communication will ensue.

The ECCluster_Listener is configured in the ecelerity-cluster.conf file. The following is an example configuration:

ECCluster_Listener {
  Listen "*:4802" {}
}

For details about the non-module specific configuration options that are valid in the ECCluster_Listener scope, refer to Configuration Options Summary .

Modules and their configuration options are discussed in the Modules Reference .

For general information regarding listeners, see “Listeners”.

Msgcserver_Listener Configuration

The msgcserver_listener mediates between msgc_servers and between msgc_servers and their clients. It is an internal service for msgc communication and is configured in the msgc_server.conf file. The following is a typical configuration:

msgcserver_listener {
   Listen ":4809" { }
}

As with other listeners, a Listen scope is defined within the msgcserver_listener. This scope defines the port on which the listener listens. By default, the msgcserver_listener listens on port 4809.

For details about the non-module specific configuration options that are valid in the msgcserver_listener and its nested scopes, refer to Configuration Options Summary .

Modules and their configuration options are discussed in the Modules Reference .

For general information regarding listeners, see “Listeners”.