3.1.2 Matrix Server Administration Guide

Chapter 13: Configure Device Monitors 184

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 shared device or 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 for script ordering.

SERIAL. This is the default setting. When a shared device or 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 shared

device or 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

or shared device is becoming active.

The SERIAL setting considers events and takes precedence over the

setting for Event Severity.

PARALLEL. Matrix Server does not enforce the strict ordering sequence

for Stop and Start scripts. The scripts run in parallel across the matrix as a

shared device or virtual host is in transition.

The PARALLEL

configuration can speed up failover time for services and

devices that do not depend on strict ordering of Start and Stop scripts.

Assuming that it is safe to run the scripts in parallel (which depends on

your application), this setting can also increase the chances of a successful

failover because Matrix Server does not have to wait for the failing node

to finish running its Stop script.