Figure HA-1 · Anatomy
The building blocks of rConfig HA
Every layer of a highly available rConfig, and how each one is made redundant
rConfig
Client traffic
VIP
Virtual IP
Heartbeat
Active node connection
Connects after failover
Replication
01 · TRAFFIC
One address
Users, integrations and Vector agents reach rConfig on the VIP
02 · APPLICATION
rConfig V8 nodes
Two identical nodes. keepalived decides which one is active
03 · DATA
Data services
Database, Redis or Valkey, and storage, each redundant on its own
04 · KEYS
Shared secrets
Same keys on both nodes
Users
Integrations
Vector agents
VIP 192.0.2.10
VIP moves here on failover
Node A · rConfig V8
ACTIVE
All services running
Webrunning
APIrunning
Schedulerrunning
Horizonrunning
Node B · rConfig V8
PASSIVE
Same install, services stopped
Webstopped
APIstopped
Schedulerstopped
Horizonstopped
keepalived
Database
Primary and replica
primary
replica
Redis or Valkey
Primary, replica and 3 Sentinels
primary
replica
Sentinel 1
Sentinel 2
Sentinel 3
Storage
Shared or replicated
Shared mount
or
Replicated copy
VIP 192.0.2.30
VIP 192.0.2.40
Node B connects only after failover
.env and APP_KEY · identical on both nodes
Node A
Node B