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.

Chapter 7 Monitor resource details<br />

584<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 />

Pending<br />

appli1<br />

Start<br />

Application<br />

Application monitor<br />

Application aborted<br />

Monitor wait time/activating/deactivating<br />

Deactivating<br />

/activating<br />

Start<br />

monitoring<br />

Request reactivation<br />

Activated<br />

Application aborted<br />

Waiting to start<br />

monitoring<br />

Monitor resource<br />

polling<br />

Monitor<br />

Waiting to start<br />

monitoring<br />

Monitor resource<br />

polling<br />

0<br />

60<br />

stopped 0 60<br />

No error is detected<br />

No error is detected<br />

because monitoring is An error is detected because monitoring is<br />

started<br />

and appli1 is reactivated<br />

started<br />

Monitor wait time – active range<br />

Request failover<br />

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

If the application is abnormally terminated in the destination server of the group failover, the<br />

group stops as the final action.<br />

When Stop cluster service and shutdown OS or Stop cluster service daemon and reboot OS<br />

is selected as a final action to be taken when an error is detected by the monitor resource, the<br />

number of shutdowns or reboots can be limited.<br />

Note:<br />

The maximum reboot count is on a server basis because the number of reboots is recorded on a<br />

server basis.<br />

The number of reboots caused by a final action in detection of error in group<br />

activation/deactivation and the number of reboots caused by a final action in detection of error by<br />

a monitor resource are recorded separately.<br />

If the time to reset the maximum reboot count is set to zero (0), the number of reboots will not be<br />

reset.<br />

The following is an example of the process when the number of reboots is limited.<br />

As a final action, Stop cluster service and reboot OS is executed once because the maximum<br />

reboot count is set to one.<br />

When the monitor resource finds no error in its target <strong>for</strong> 10 minutes after reboot following<br />

cluster shutdown, the number of reboots is reset because the time to reset the maximum reboot<br />

count is set to 10 minutes.<br />

Monitor<br />

stopped<br />

Failover to the next<br />

policy server<br />

Time<br />

An error is detected and group fail<br />

over takes place<br />

Monitoring stopped range<br />

<strong>ExpressCluster</strong> X <strong>2.0</strong> <strong>for</strong> <strong>Windows</strong> <strong>Reference</strong> <strong>Guide</strong>

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

Saved successfully!

Ooh no, something went wrong!