I know it's a simple and seemlingly goofy question, but the reason I'm
asking is because of the great spikes in load average that occur
during reload. I see it go from <1 to >40. I want to understand this
and minimize it. I've got 20,000 service checks and 2,000 hosts
defined in a three or four dozen .conf files, the largest of which
contains 75,000 lines and 1700 "object Host" defined. But I suspect
the culprit is not quantity, but rather the processing incurred by
functions that iterate through get_objects(Host) which are in multiple

In any case, I would like to try to minimize the spikes in load
average. I've seen some mention of this problem in other threads and
forums, without any solutions other than throwing more cores at the

On Wed, Nov 30, 2016 at 9:26 AM, Michael Martinez <mwt...@gmail.com> wrote:
> Is "service icinga2 reload" necessary anytime a config file changes,
> or does icinga2 automatically recognize if the file changes?
> What's the difference between reload and restart and under which
> circumstances is one used instead of the other?
> --
> ---
> Michael Martinez
> http://www.michael--martinez.com

Michael Martinez
icinga-users mailing list

Reply via email to