Skip to content

Broker Redundancy

Configure primary and secondary MQTT brokers for automatic failover.

Broker Redundancy Screenshot placeholder: Broker redundancy configuration

How It Works

  1. Gateway connects to primary broker
  2. Publishes all data normally
  3. If primary fails → automatic failover to secondary
  4. Background monitor checks primary availability
  5. Auto-reconnect to primary when recovered

Configuration

Set Up Brokers

  1. Create primary broker (see MQTT Brokers)
  2. Create secondary broker
  3. Test both connections

Configure Edge Node

Node Broker Config Screenshot placeholder: Node broker selection

  1. Edit edge node
  2. Select Primary Broker
  3. Select Secondary Broker
  4. Save

Failover Behavior

Detection

  • Primary connection lost
  • Keep-alive timeout
  • Write failure

Switchover

  • Disconnect from primary
  • Connect to secondary
  • Publish NBIRTH to secondary
  • Resume normal operation

Recovery

  • Background task monitors primary
  • When available, reconnect to primary
  • Publish NBIRTH to primary
  • Resume normal operation

Best Practices

  • Use different servers for redundancy
  • Test failover scenarios
  • Monitor both brokers
  • Keep credentials synchronized

Next Steps