Bugzilla – Bug 5320
Control the number of active IM MADs
Last modified: 2007-06-06 07:18:27
You need to
before you can comment on or make changes to this bug.
Control the number of active IM MADs, since they can overload the system if
there are many hosts to monitor.
The number of active IM MADs will be kept to a (soft) limit. Every time a
discovery or monitoring process starts, the number of active IM MADs will be
increased, and every time a discovery or monitoring process ends, this number
will be decreased. No new monitoring actions will be started if this number
exceeds the maximum. This does not apply to discovery actions, since only one
is periodically performed per IM MAD and we don't expect a high number of IM
1. New parameter MAX_ACTIVE_IM_MADS in gwd.conf.
2. Modified discovery and monitoring process.
Changes committed to CVS (FALCATA branch).
Actually, it is not the number of active IM MADs, but the number of processes
spawned by IM MADs (one process per outstanding query).
New parameter MAX_ACTIVE_IM_QUERIES in gwd.conf.