Multicast behaviour and interface address

Knowledge Base Network
1

The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.

Multicast behaviour and interface address

Summary

In aerospike versions 3.10+ you can specify which interface address, or addresses, you want to send multicast messages from. This is particularly important if you are using VLAN interfaces and mutlicast messaging does not otherwise repeat across them.

Usage

To specify multiple addresses for multicast, use the address configuration in the heartbeat stanza multiple times. Below example sends from 2 interfaces, to which the ‘address’ IPs are assigned:

heartbeat {
	mode multicast
	multicast-group 239.1.99.222
	port 9918
	interval 150
	timeout 10

	address 10.0.100.27
	address 192.168.0.40
}

Versions up to 3.9

If you are using an aerospike version older than 3.10, this feature isn’t available. You can specify which address to send multicast messages from using the interface-address configuration parameters, although this will only allow you to specify a single address. Using multiple interface-address is not permitted. Example below:

heartbeat {
	mode multicast
	multicast-group 239.1.99.222
	port 9918
	interval 150
	timeout 10

	interface-address 10.0.100.27
}

Notes

The IP address is the address that will be published by the node in the heartbeat messages as well as being used to decide which interface(s) to send HB messages on.

If no interface-address or address are used, Aerospike will use the default interface specified in the service context.

Keywords

MUTLICAST INTERFACE NETWORK ADDRESS INTERFACE-ADDRESS

Timestamp

10/29/2018