Configuring Well-Known Address Cluster Discovery

You can add up to nine well-known addresses. If you need to add more refer to Coherence documentation for instructions about using override files.

To configure well-known address discovery, you must configure machine-specific settings at the cluster level and at the processing unit level. One processing unit deployed to a WKA machine must have the additional WKA configuration. Additional processing units can be deployed to a WKA machine, configured in the usual way, and they will discover and join the cluster in the usual way at runtime.

For details about the properties, see Well-Known Address Properties.

Procedure

  1. In the CDD file editor Cluster tab properties sheet, add a pair of WKA properties for each machine you want to configure as a well-known address machine:
    tangosol.coherence.wkan HostIP

    tangosol.coherence.wkan.port Hostport

    For example at the cluster level you might have these two WKA machines:

    Property: tangosol.coherence.wka1       Value: 10.97.118.151
Property: tangosol.coherence.wka1.port  Value: 8098

    Property: tangosol.coherence.wka2       Value: 10.97.118.152
Property: tangosol.coherence.wka2.port  Value: 8098

    Note: If two engines run on one machine (with a single IP), ensure that each engine uses a different port. For example:

    Property: tangosol.coherence.wka1       Value: 10.97.118.151
Property: tangosol.coherence.wka1.port  Value: 8098

    Property: tangosol.coherence.wka2       Value: 10.97.118.151
Property: tangosol.coherence.wka2.port  Value: 8099

  2. In the Processing Units tab properties sheet for a processing unit (PU), configure one set of WKA properties to match one of the cluster level set of WKA properties:
    tangosol.coherence.localhost HostIP

    tangosol.coherence.localport Hostport

    Set the localhost property to the IP of the host where you will deploy the PU, and set the localport property to the port defined in the cluster properties localport property.

  3. Repeat the previous step until you have configured a PU with matching PU-level properties for each cluster-level (that is, machine-level) set of WKA properties.

    For example, if you configured the two well-known addresses, then at the processing unit level you would configure two processing units as follows:

    tangosol.coherence.localhost. Value: 10.97.118.151
tangosol.coherence.localport. Value: 8098

    tangosol.coherence.localhost. Value: 10.97.118.152
tangosol.coherence.localport. Value: 8098

    At deploy time you must deploy the processing units on the appropriate (matching) WKA machine. It can be helpful if the name of the PU contains the machine name as a reminder that this PU must be deployed to that machine.

    See Localhost and Localport Properties.