The port-based-config section of the Aerospike ESP Outbound YAML file

Use the port-based-config section to configure alternate ports to receive change notifications.

This is useful, for example, when you want to ship the same change notification to multiple destinations using a single connector cluster. To do this, configure XDR to ship to different ports on the same connector instance. Then set up each port to apply different configurations to dispatch the change notifications. For this you create one DC on XDR per connector port.

info

You can use any port between 1024 and 65335 for Aerospike, as long as the port is not in use by an existing process.

For any service port you can configure any or all of the following differently from the global configuration

• routing
• format
• bin-transforms
• namespaces

Example

This example routes records to alternate destinations based on the incoming port.

port-based-config:
  8901:
    routing:
      mode: static-multi-destination
      destinations: xdr-proxy1
  9901:
    routing:
      mode: static-multi-destination
      destinations: xdr-proxy2