3.1.2 Matrix Server Administration Guide

Chapter 12: Configure Service Monitors 168

NOAUTORECOVER. The virtual host fails over when a monitor probe

fails and the monitor is disabled on the original node, preventing

automatic failback. When the monitor is reenabled, failback occurs

according to the virtual host’s failback policy.

The

NOAUTORECOVER option is useful when integrating Matrix Server

with a custom application where certain application-specific actions must

be taken before the failback can occur.

For more information on the interaction between the Timeout and Failure

Severity attribute and the virtual host failback policy, see “Virtual Hosts

and Failover” on page 154.

To set the Timeout and Failure Severity attribute from the command line,

use this option:

--probeSeverity nofailoverautorecover|noautorecover

Service Priority

The service priority is used by Matrix Server when it fails over services.

Service priorities are natural numbers, with 0 (zero) representing the

highest priority and higher numbers representing lower priorities. If

multiple failures prevent Matrix Server from placing a virtual host on a

server where all of its associated services are available, Matrix Server next

looks for a server where the associated service with the highest priority is

available. By default, all service monitors have a priority of 0.

To set the Service Priority from the command line, use this option:

--priority <priority>

Probe Type

The probe type applies only to

CUSTOM service monitors. These monitors

can be configured to be either single-probe or multi-probe. A multi-probe

monitor performs the probe function on each node where the monitor is

configured, regardless of whether the monitor instance is active or

inactive. The built-in monitors work in this manner.

Single-probe monitors perform the probe function only on the node

where the monitor instance is active. This type of configuration is useful

for applications such as databases that are not cluster-aware and should

be run on only one node at a time. The monitor instance is activated on