GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  CRMD (7)

.ds Aq ’

NAME

crmd - CRM Daemon Options

CONTENTS

SYNOPSIS

[dc-version=string] [cluster-infrastructure=string] [dc-deadtime=time] [cluster-recheck-interval=time] [load-threshold=percentage] [node-action-limit=integer] [election-timeout=time] [shutdown-escalation=time] [crmd-integration-timeout=time] [crmd-finalization-timeout=time] [crmd-transition-delay=time] [stonith-watchdog-timeout=time]

DESCRIPTION

This is a fake resource that details the options that can be configured for the CRM Daemon.

SUPPORTED PARAMETERS

dc-version = string [none]

Version of Pacemaker on the clusters DC.

Includes the hash which identifies the exact changeset it was built from. Used for diagnostic purposes.

cluster-infrastructure = string [heartbeat]

The messaging stack on which Pacemaker is currently running.

Used for informational and diagnostic purposes.

dc-deadtime = time [20s]

How long to wait for a response from other nodes during startup.

The "correct" value will depend on the speed/load of your network and the type of switches used.

cluster-recheck-interval = time [15min]

Polling interval for time based changes to options, resource parameters and constraints.

The Cluster is primarily event driven, however the configuration can have elements that change based on time. To ensure these changes take effect, we can optionally poll the clusters status for changes. Allowed values: Zero disables polling. Positive values are an interval in seconds (unless other SI units are specified. eg. 5min)

load-threshold = percentage [80%]

The maximum amount of system resources that should be used by nodes in the cluster

The cluster will slow down its recovery process when the amount of system resources used (currently CPU) approaches this limit

node-action-limit = integer [0]

The maximum number of jobs that can be scheduled per node. Defaults to 2x cores

election-timeout = time [2min]

*** Advanced Use Only ***.

If need to adjust this value, it probably indicates the presence of a bug.

shutdown-escalation = time [20min]

*** Advanced Use Only ***.

If need to adjust this value, it probably indicates the presence of a bug.

crmd-integration-timeout = time [3min]

*** Advanced Use Only ***.

If need to adjust this value, it probably indicates the presence of a bug.

crmd-finalization-timeout = time [30min]

*** Advanced Use Only ***.

If you need to adjust this value, it probably indicates the presence of a bug.

crmd-transition-delay = time [0s]

*** Advanced Use Only *** Enabling this option will slow down cluster recovery under all conditions

Delay cluster recovery for the configured interval to allow for additional/related events to occur. Useful if your configuration is sensitive to the order in which ping updates arrive.

stonith-watchdog-timeout = time [(null)]

How long to wait before we can assume nodes are safely down

AUTHOR

Andrew Beekhof <andrew@beekhof.net>

Author.
Search for    or go to Top of page |  Section 7 |  Main Index


Pacemaker Configuration CRM DAEMON (7) 04/05/2016

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.