Section 11. Using Gossip framework

11. Using Gossip framework

Radiator's Gossip framework allows Radiator instances to share information and event notifications. The instances can be part of server farm, completely separate processes running on the same or different hosts, or any combination of thereof.

Radiator's Gossip framework supports the following backends:

GossipRedis clause is used to configure a Redis-based Gossip framework instance. For more information, see Section 3.134. <GossipRedis>.
GossipUDP clause is used to configure a UDP-based Gossip framework instance. For more information, see Section 3.135. <GossipUDP>.

Currently the following Radiator modules support Gossip:

<AuthBy RADIUS> and its subclasses can use GossipRedis for communicating next hop host unreachability and reachability information with Gossip messages. Multiple Radiator instances, in both stand-alone and FarmSize configuration, can share proxy status information. This allows, for example, just one member to run Status-Server queries when FarmSize configuration parameter is enabled.
<AuthBy RADSEC> support is similar to <AuthBy RADIUS>.
Radius Clients can use GossipRedis for duplicate cache. When the global configuration parameter DupCache is set to global, GossipRedis is used for RADIUS duplicate cache.
StatsLog REDIS uses GossipRedis for storing statistics in Redis.

Gossip message format supports optional header for TTL, payload encryption, and future extensions.

More Radiator modules will be added and upgraded to use the Gossip framework in the future. You can also create customised modules for your requirements. Radius::Gossip module provides the common API for all Gossip implementations such as GossipRedis and GossipUDP.