27.02.2013 Views

ExpressCluster X 2.0 for Windows Reference Guide - Nec

ExpressCluster X 2.0 for Windows Reference Guide - Nec

ExpressCluster X 2.0 for Windows Reference Guide - Nec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

appli1<br />

Section II Resource details<br />

Monitor resources<br />

For example, when the monitor wait time is set to 0 (zero), recovery may be endlessly repeated.<br />

See the example below:<br />

Configuration of application monitor resource<br />

<br />

Interval 5 sec<br />

Timeout 60 sec<br />

Retry Count Zero<br />

Wait Time to Start Monitoring 0 sec (default)<br />

<br />

Recover Target appli1<br />

Reactivation Threshold 1<br />

Failover Threshold 1<br />

Final Action Stop Group<br />

Start activating group<br />

Activating Activated<br />

Application<br />

Start<br />

Application monitor<br />

Monitor resource<br />

polling<br />

Monitoring finding<br />

no errors<br />

Monitor wait time / Activating<br />

/ Inactivating<br />

Application aborted<br />

deactive/activating<br />

Start monitoring<br />

Request reactivation<br />

Monitor resource<br />

Interval polling Monitor<br />

stopped<br />

An error is detected<br />

and appli1 is<br />

Normal monitoring<br />

reactivated.<br />

Monitor wait time –<br />

Range of activation<br />

Start<br />

Monitor resource<br />

polling<br />

Activated<br />

Application aborted<br />

Time <strong>for</strong> monitor processing Normal rang of time <strong>for</strong> monitor processing<br />

Deactivating/activatin<br />

Start monitoring<br />

Request reactivation<br />

Monitor resource<br />

Interval polling<br />

Monitor<br />

stopped<br />

Start<br />

An error is detected<br />

and appli1 is<br />

reactivated<br />

Monitoring Range of<br />

stopping<br />

The reason why recovery action is endlessly repeated is because the initial monitor resource<br />

polling has terminated successfully. The current count of recoveries the monitor resource has<br />

executed is reset when the status of the monitor resource becomes normal (finds no error in the<br />

monitor target). Because of this, the current count is always reset to 0 and reactivation <strong>for</strong><br />

recovery is endlessly repeated.<br />

You can prevent this problem by setting the wait time to start monitoring. By default, 60 seconds<br />

is set as the wait time from the application startup to the end.<br />

Configuration of application monitor resource<br />

<br />

Interval 5 sec<br />

Timeout 60 sec<br />

Retry Count Zero<br />

Wait Time to Start Monitoring 60 sec<br />

Time<br />

583

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!