Keepalived normally will open three processes, including the parent, child and healthchecker VRRP child process,

Currently in use to find a strange phenomenon, in the use of keepalived + the LVS forward load balancing, occasionally found in four processes, the process is as follows, you can see, the process of the temporary appear healthchecker process as part of the process, the instantaneous appear soon disappeared after,

| - keepalived (15647) - + - keepalived (15648)
| ` - keepalived (15649) - keepalived (560)

Keepalived is configured with two LVS virtual_server, each configuration two real_server backend, using NAT + rr model, two LVS configuration is as follows:
Virtual_server 192.168.182.172 514 {
Delay_loop 3
Lb_algo rr
Lb_kind NAT
Nat_mask 255.255.255.0
# persistence_timeout 50
Protocol UDP
Real_server 192.168.182.188 1025 {
The weight of 1
TCP_CHECK {
Connect_timeout 3
Nb_get_retry 2
Delay_before_retry 1
Connect_port 8080
}
}
Real_server 192.168.182.189 1025 {
The weight of 1
TCP_CHECK {
Connect_timeout 6
Nb_get_retry 2
Delay_before_retry 2
Connect_port 8080
}
}
}

Virtual_server 192.168.182.173 514 {
Delay_loop 3
Lb_algo rr
Lb_kind NAT
Nat_mask 255.255.255.0
# persistence_timeout 50
Protocol UDP
Real_server 192.168.182.190 1025 {
The weight of 1
TCP_CHECK {
Connect_timeout 3
Nb_get_retry 2
Delay_before_retry 1
Connect_port 8080
}
}
Real_server 192.168.182.191 1025 {
The weight of 1
TCP_CHECK {
Connect_timeout 3
Nb_get_retry 2
Delay_before_retry 1
Connect_port 8080
}
}
}

Ask why there will be a temporary keepalived process, this process is what?