Skip to main content
Loading

The routing section of the Aerospike ESP Outbound YAML file

The routing section of the /etc/aerospike-esp-outbound/aerospike-esp-outbound.yml controls how Aerospike records are routed to an ESP destination that was configured in the destinations section.

The following routing modes are available.

  • static-multi-destination List of destinations to route to.
  • skip Skip dispatch of record to the destination and ack success to XDR.
  • custom Route with custom code.

Static Multi Destination Routing

This routing is used to send the same change notification record to multiple destinations.

danger

The connector sends a successful ack to XDR if and only if a record shipping succeeds on all the destinations. If any of the destination fails, XDR receives a failure ack and the same change notification record is triggered again. The caveat here is that all the destinations will receive the change notification record again, even though some of them successfully processed in the previous attempt.

For static-multi-destination routing, the configuration options are:

OptionRequiredDefaultDescription
modeyesShould be static-multi-destination .
destinationsyesList of destination names configured the destinations section.

Example

  routing:
mode: static-multi-destination
destinations:
- "xdr-proxy1"
- "xdr-proxy2"

Skip routing

For skip routing, the configuration options are:

OptionRequiredExpected valueDescription
modeyesskipSkip dispatch of record to the destination and ack success to XDR.

Example

routing:
mode: skip

Custom Routing

Record can be also be routed with custom code. See Routing Transform.

Example

routing:
mode: custom
class: com.aerospike.connect.outbound.example.GenerationRouter