Configuring an ESP Cluster to Communicate on a Specific Network Card

If the machine hosting Event Stream Processor is equipped with more than one network card, you can configure the cluster to use a specific card for all network communication.

  1. Use a text editor to open the configuration file from ${ESP_HOME}/cluster/nodes/<node-name>/<node-name>.xml.
    By default, the Event Stream Processor installation process creates a cluster configuration file called node1.xml. If you specified a different name for your cluster, the cluster configuration file will be named <node-name>.xml.
  2. Define the host node for the RPC port.
    In the <Host> parameter, replace <thehostname> with the designated IP address of the NIC you want the cluster to use.
    <Host><thehostname></Host>
  3. Define the host node for the cache.
    In the cache <Host> parameter, replace <thehostname> with the designated IP address of the network interface card you want the cluster to use.
    <Host><thehostname></Host>
    Note: If the machine is set to use a proxy server or is behind a firewall, you may be unable to start a project when ESP is configured to use a network card other than the default. In such cases, ensure that any system communicating with ESP is added to the no_proxy environment variable, as follows: 
    no_proxy='espinstance.mycomp.com,espinstance, .mycomp.com'

    Include the fully-qualified name as illustrated in the example. In some cases, you may also have to add the ESP machine's IP address. Also verify that there are no inconsistent entries in the /etc/hosts file. This configuration applies to any ESP client system as well as any ESP-to-ESP communication.

    If using the no_proxy environment variable causes communication issues such as HTTP Error 503 Service unavailable, you can disable the proxy by unsetting the http_proxy environment variable .

Parent topic: Configuring End-to-End Communication on Non-Default Network Cards