Hello,
I have deployed an HA satellite setup, with two satellite within the same zone. I was expecting the satellites to load-balance my checks as per documentation. However, looking at tcpdump outrouts, the checks (hostalive) are performed by both satellites instead.
High-level info
- Incinga :
r2.13.1-1
- Operating System :
Ubuntu 20.04.3 LTS
with5.4.0-1045-aws
kernel. - Enabled features (master) :
api checker ido-pgsql influxdb2 mainlog notification
- Enabled features (satellites) :
api checker mainlog
Config files
zones.conf - master
object Zone "global-templates" {
global = true
}
object Endpoint "master01.lab" { }
object Zone "master" {
endpoints = [ "master01.lab" ]
}
object Endpoint "satellite01.lab" {
# log_duration = 0 # Use command mode instead; does not help.
}
object Endpoint "satellite02.lab" {
# log_duration = 0 # Use command mode instead; does not help.
}
object Zone "satellite-germany" {
endpoints = [ "satellite01.lab", "satellite02.lab" ]
parent = "master"
}
zones.conf - satellites
object Zone "global-templates" {
global = true
}
object Endpoint "master-01.lab" {
host = "10.0.10.100"
}
object Zone "master" {
endpoints = [ "master-01.lab" ]
}
object Endpoint "satellite01.lab" {
# log_duration = 0 # Use command mode instead; does not help.
# host = "10.0.20.150" # Let sattelite02 connect to sattelite01; does not help.
}
object Endpoint "satellite02.lab" {
# log_duration = 0 # Use command mode instead; does not help.
}
object Zone "satellite-germany" {
endpoints = [ "satellite01.lab", "satellite02.lab" ]
parent = "master"
}
Host
object Host "ExampleHost" {
address = "10.20.50.222"
check_command = "hostalive"
check_interval = 2m
max_check_attempts = 10
zone = "satellite-germany"
}
Tcpdump
Example tcpdump output below; both satellite pings the host every 2mn.
satellite01
09:58:01.375136 IP 10.0.20.150 > 10.20.50.222: ICMP echo request, id 58014, seq 1, length 64
09:58:01.403512 IP 10.20.50.222 > 10.0.20.150: ICMP echo reply, id 58014, seq 1, length 64
10:00:01.374583 IP 10.0.20.150 > 10.20.50.222: ICMP echo request, id 59444, seq 1, length 64
10:00:01.402910 IP 10.20.50.222 > 10.0.20.150: ICMP echo reply, id 59444, seq 1, length 64
10:02:01.374966 IP 10.0.20.150 > 10.20.50.222: ICMP echo request, id 60877, seq 1, length 64
10:02:01.403399 IP 10.20.50.222 > 10.0.20.150: ICMP echo reply, id 60877, seq 1, length 64
10:04:01.373899 IP 10.0.20.150 > 10.20.50.222: ICMP echo request, id 62305, seq 1, length 64
10:04:01.402275 IP 10.20.50.222 > 10.0.20.150: ICMP echo reply, id 62305, seq 1, length 64
satellite02
09:58:54.774500 IP 10.0.20.160 > 10.20.50.222: ICMP echo request, id 36910, seq 1, length 64
09:58:54.804295 IP 10.20.50.222 > 10.0.20.160: ICMP echo reply, id 36910, seq 1, length 64
10:00:54.773566 IP 10.0.20.160 > 10.20.50.222: ICMP echo request, id 38343, seq 1, length 64
10:00:54.803389 IP 10.20.50.222 > 10.0.20.160: ICMP echo reply, id 38343, seq 1, length 64
10:02:54.773816 IP 10.0.20.160 > 10.20.50.222: ICMP echo request, id 39768, seq 1, length 64
10:02:54.803616 IP 10.20.50.222 > 10.0.20.160: ICMP echo reply, id 39768, seq 1, length 64
10:04:54.773972 IP 10.0.20.160 > 10.20.50.222: ICMP echo request, id 41196, seq 1, length 64
10:04:54.803758 IP 10.20.50.222 > 10.0.20.160: ICMP echo reply, id 41196, seq 1, length 64