[Linux-HA] two monitor

[Andrew Beekhof]

On 5/9/07, benjamin <benjamin.parmentier at gmail.com> wrote:
> Hi,
>
> I see here, http://www.linux-ha.org/ClusterInformationBase/Actions, that we
> can set different interval and paramters to a monitor but is it possible to
> have two (or more) monitors for a same resource ?
>
> For example : is it possible to have a monitor checking the connectivity of
> a mysql server each 10s and another monitor that check the mysql server with
> an SQL request each 15min ?

sure.

you can run as many monitors as you like and to get them to perform
more/less intensive checks, i recommend reading section 3.5.3.1 of the
OCF spec.  basically you set a attribute called OCF_CHECK_LEVEL for
each monitor action.

eg.
             <op id="rsc_c001n08-1" name="monitor" interval="5s" timeout="21s">
               <instance_attributes ="foo">
		 <attributes>
		   <nvpair id="some-attr" name="OCF_CHECK_LEVEL" value="10"/>
		 </attributes>
               </instance_attributes>
	     </op>

3.5.3.1. Parameters specific to the 'monitor' action

OCF_CHECK_LEVEL
	0	The most lightweight check possible, which should not
		have an impact on the QoS.
		Example: Check for the existence of the process.
	10	A medium weight check, expected to be called multiple
		times per minute, which should not have a noticeable
		impact on the QoS.
		Example: Send a request for a static page to a
		webserver.
	20	A heavy weight check, called infrequently, which may
		impact system or service performance.
		Example: An internal consistency check to verify service
		integrity.

	Service must remain available during all of these operation.
	All other number are reserved.

	It is recommended that if a requested level is not implemented,
	the RA should perform the next lower level supported.


>
> If it's possible how to write it in the OCF scripts ???
>
> Thanx.
>
> --
> benjamin
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>