3.6.0 Matrix Server 3.6.0 Administration Guide (5697-7081, December 2007)

Chapter 16: Configure Service Monitors 205

PARALLEL. The strict ordering sequence for Stop and Start scripts is not

enforced. The scripts run in parallel across the matrix as a virtual host 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

failover because ClusterPulse does not have to wait for the failing server

to finish running its Stop script.

To configure script ordering from the command line, use this option:

--ordering serial|parallel

Other Configuration Procedures

These procedures can be performed from the Servers, Virtual Hosts, or

Applications tabs on the PolyServe Management Console or from the

command line.

Delete a Service Monitor

From the Management Console, select the service monitor to be deleted,

right-click, and select Remove From Server.

To delete a service monitor from the command line, use this command:

mx service delete <vhost:port>

Disable a Service Monitor on a Specific Server

When a monitor is disabled, the health of the server is affected in the

same manner as a failure of the monitor’s probe operation. If the Policy

configuration of the monitor is either

AUTORECOVER or

NOAUTORECOVER, the ClusterPulse process will attempt to fail over the

virtual host associated with the monitor to a backup node. If a backup

node is not available or if the Policy configuration of the monitor is

NOFAILOVER, the virtual host will remain on the original node. The

monitor will continue probing and will report the status of the service as

UP or DOWN as appropriate. If the service is UP, the monitor will report

UP Active (disabled).