3.1.2 MxFS-Linux Administration Guide

Chapter 2: Configure Export Groups 27

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

There are two settings:

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

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 the Start and Stop scripts

are run when a Virtual NFS Service moves from one node to another. If

you do not configure Start and Stop scripts for an Export Group, the

script ordering configuration has no effect.

There are two settings for script ordering.

SERIAL. This is the default setting. When a Virtual NFS Service moves

from one node 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 nodes where the Virtual NFS

Service should be inactive.

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

3. Matrix Server runs the Start script on the node where the Virtual NFS

Service is becoming active.

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

Virtual NFS Service is in transition.

The PARALLEL

configuration can speed up failover time for services 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