[omd-users] OMD 2.60 - Activate Changes taking too long

Andreas Döhler andreas.doehler at gmail.com
Sat Sep 16 10:14:37 CEST 2017

Hi Mahesh,

One option you have is to split your setup to more then one site. It is
possible to run some sites (4-5) without problems on the same host and do
the configuration from only one of these sites.
I have some setups with hosts between 1000 and 2000 and only around 500 per
site. Now if i configure some changes only for one sub-folder inside WATO
only the site theses hosts belong to are restarted.
With such a setup there is only one restriction. It is not possible to have
parent child relations across sites.


Mahesh Patade <patademahesh at gmail.com> schrieb am Sa., 16. Sep. 2017 um
09:11 Uhr:

> Hi All,
> Recently we upgraded our OMD from 1.20 to 2.60. We are monitoring approx.
> 1500 hosts and 32k services. Everything is working fine except "Activate
> changes" task. It takes around 10-15 minutes to make changes.
> When i checked in the background it runs check_mk.py - automation -
> restart task which iterates over pre-compiled checks for all the hosts
> monitored from that OMD instance. Which in turns takes so much time because
> its a synchronous process.
> Is there any we can run this only for changed services/hosts OR make this
> process run parallel ?
> Thanks a lot for such a wonderful gift to OSS community.
> Best Regards,
> Mahesh
> _______________________________________________
> omd-users mailing list
> omd-users at lists.mathias-kettner.de
> http://lists.mathias-kettner.de/mailman/listinfo/omd-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mathias-kettner.de/pipermail/omd-users/attachments/20170916/753df44c/attachment-0001.html>

More information about the omd-users mailing list