Previous page

Next page

Locate page in Contents

Print this page

shaman.conf

The /etc/shaman/shaman.conf file is used by the shaman utility to manage and monitor High Availability clusters and cluster resources.

Format

<parameter_name> = <parameter_value>

Options

Name

Description

CLUSTER_NAME

Set the name of the cluster for shaman to operate on.

LOG_LEVEL

Set the verbosity level for printed messages:

  • 0. Print error messages only.
  • 1. Print warning messages in addition to error messages.
  • 2. Print information messages in addition to error and warning messages. This is the default verbosity level.
  • 4. Print debug diagnostic messages in addition to messages from level 0-2.

LOCK_TIMEOUT

Set the timeout for shaman-monitor operations (e.g., electing a new master or deciding that a slave node is down). This parameter helps avoid situations when shaman-monitor performs a cluster-related operation if someone pulls out the network cable for just a couple of seconds (not longer than the half of the LOCK_TIMEOUT value).

The default value is 60 seconds.

The specified value is added to the value of other timeout-related parameters (see below).

LEASE_CHECK_TIMEOUT_FOR_MASTER

Set the timeout for electing a new master node when the original master node or the shaman-monitor daemon fails, or high availability support gets disabled.

The default value is 10 seconds.

LEASE_CHECK_TIMEOUT_FOR_SLAVE

Set the timeout after which the master node will consider a slave node as broken if this node and the shaman-monitor daemon get down, or high availability support gets disabled.

The default value is 10 seconds.

LEASE_LOST_ACTION

Defines the action to perform if shaman-monitor loses connection to cluster.

This may happen when a node goes online after having been disconnected from network for more than LOCK_TIMEOUT seconds. In this case, the watchdog timer has not expired yet, but the cluster is already unavailable, because the master node has prohibited access to the cluster until the node is rebooted.

Available values are crash , halt , reboot , and none (do nothing).

POOL_CHECK_TIMEOUT

Set the interval for shaman-monitor to check for the resources scheduled for relocation.

The default value is 30 seconds.

RELOCATION_SKIP_THRESHOLD

Sets the threshold for the number of simultaneously crashed nodes.

If the number of simultaneously crashed nodes becomes greater than or equal to the threshold, the master stops relocating resources from the crashed nodes. When the number of simultaneously crashed nodes drops below the threshold, the master automatically resumes relocating resources from the crashed nodes. The threshold can be useful when multiple nodes are being rebooted at the same time. Without it, the master would start relocating resources from all the rebooting nodes.

The threshold is set to 3 by default and must be 2 or greater. For clusters with only 3 nodes, the threshold is automatically set to 2.

WATCHDOG_TIMEOUT

Set the interval for the watchdog timer.

The watchdog timer is responsible for performing the action defined in WATCHDOG_ACTION (see below) if shaman-monitor crashes or hangs up. The shaman-monitor daemon activates the watchdog timer on its start-up and periodically resets it to the specified value. If something goes wrong with shaman-monitor so that it fails to reset the timer, the watchdog timer counts down until it reaches zero and performs the defined action. Setting the interval to zero disables the watchdog timer. Minimal watchdog timer interval that could be set is 10 seconds.

The default value is 120 seconds.

WATCHDOG_ACTION

Defines a sequence of actions to perform after the watchdog timer expires (happens when shaman-monitor crashes or hangs up) .

When the watchdog timer expires, the first specified action is attempted. If unsuccessful, the next specified action is attempted and so on. If the last specified action is unsuccessful, then the action specified in the /sys/kernel/watchdog_action file is performed.

At least one action must be specified. Multiple actions must be separated with commas. Available actions are listed in the /sys/kernel/watchdog_available_actions file. The default sequence is netfilter, reboot .