Satellite config sync and load balancing

Icinga 2
,
1

Hello,

I’m trying to understand these 2 processes which are interleaved with each other. I’ve been seeing this problem where checks stay into “UNKNOWN” state for > 10minutes after a config change is made on the Icinga master. As per my understanding, a config change will reload the Icinga2 process on the masters and then on the satellites. Waiting for that long is a bit making people paranoid so I’m trying to find a way to speed up this or at least find what is causing this at the first place.

Does one small config change make full config sync across the cluster or just the delta?
Probably after the reload, the load balancing occurs on the satellites. Am I right?
Do satellite try to load balance from the scratch ( full config sync) or only deal with delta coming off the config sync?

Please advise,
Thanks

2

Hi @monigacom,
I fear I can not provide you with accurate knowledge on the topic, but would like to help.
I think, the configuration is synced in full everytime, although mostly this is a negligible amount of time in the grand scheme of things.

The config reload though, which involves compiling the config first probably takes far longer than that (much much longer depending on how the config was designed).

Now something might be off with your setup, I can not really tell without seeing it, but it might also be completely fine.
What is the Check Period on those checks?