Bug 5320 – Control the number of active IM MADs

Bug 5320 - Control the number of active IM MADs

Summary:

Control the number of active IM MADs

Status:	CLOSED FIXED

Product:	Gridway
Component:	Campaign
Version:	unspecified
Platform:	All All

Importance:	P3 blocker
Target Milestone:	---
Assigned To:	Ruben S. Montero

URL:
Keywords:

Depends on:
Blocks:	5251
	Show dependency tree / graph

Reported:	2007-05-22 06:54 by Eduardo Huedo
Modified:	2007-06-06 07:18 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Eduardo Huedo 2007-05-22 06:54:25

PURPOSE:
--------

Control the number of active IM MADs, since they can overload the system if
there are many hosts to monitor.

DETAILS:
--------

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
MADs.

DELIVERABLES:
-------------

1. New parameter MAX_ACTIVE_IM_MADS in gwd.conf.
2. Modified discovery and monitoring process.

ESTIMATED TIME:
---------------

10 hours.

------- Comment #1 From Eduardo Huedo 2007-05-25 07:54:14 -------

Changes committed to CVS (FALCATA branch).

------- Comment #2 From Eduardo Huedo 2007-05-28 06:19:44 -------

Actually, it is not the number of active IM MADs, but the number of processes
spawned by IM MADs (one process per outstanding query).

------- Comment #3 From Eduardo Huedo 2007-06-06 07:18:27 -------

New parameter MAX_ACTIVE_IM_QUERIES in gwd.conf.