3.1.2 Matrix Server Administration Guide

Chapter 12: Configure Service Monitors 171

Such a failure or timeout creates an event associated with the monitor on

the server where the failure or timeout occurred. You can view these

events on the Management Console and clear them from the Console or

command line after you have fixed the problems that caused them.

You can configure the failover behavior with the Event Severity attribute.

There are two settings:

CONSIDER. This is the default value. Events are considered when

Matrix Server makes failover decisions.

IGNORE. Events are ignored and Start or Stop script failures will not

cause failover. This is useful when the action performed by the Start and

Stop scripts is not critical, but is important enough that you want to keep

a record of it.

To configure event severity from the command line, use this option:

--scriptSeverity consider|ignore

Script Ordering

Script ordering determines the order in which Matrix Server runs Start

and Stop scripts when a virtual host moves from one server to another. If

you do not configure a monitor with Start and Stop scripts, the script

ordering configuration has no effect. There are two settings:

SERIAL. This is the default setting. When a virtual host moves from one

server to another, Matrix Server enforces the following strict ordering

sequence for running Start and Stop scripts:

1. Matrix Server runs the Stop script on all servers where the virtual host

should be inactive.

2. Matrix Server waits for all Stop scripts to complete.

3. Matrix Server runs the Start script on the server where the virtual host

is becoming active.

The SERIAL setting considers events and takes precedence over the

setting for Event Severity.