RHCS v2 cluster.conf - Revision history

Digimer: /* token */

2011-05-17T20:01:51Z

token

← Older revision		Revision as of 20:01, 17 May 2011
Line 273:		Line 273:
	=== token ===		=== token ===

	This sets the maximum amount of time, in milliseconds, the totem protocol will wait for a token. If this time elapses, the cluster will reformed which takes approximately 50 milliseconds. The reconfiguration time is, then, a sum of this value plus the reconfigure time.		This sets the maximum amount of time, in milliseconds, the totem protocol will wait for a token. If this time elapses, the cluster will reformed which takes approximately 50 milliseconds. The reconfiguration time is, then, a sum of this value times <span class="code">token_retransmits_before_loss_const</span> plus the reconfigure time (<span class="code">(4 * 1000) + 50</span> ms).

	* The default value is <span class="code">~~10000~~</span> (10 seconds).		* The default value is <span class="code">1000</span> (1 seconds).
	* This must be a [http://en.wikipedia.org/wiki/Natural_number natural number]		* This must be a [http://en.wikipedia.org/wiki/Natural_number natural number]

Digimer: /* token_retransmits_before_loss_const */

2011-05-17T19:59:41Z

token_retransmits_before_loss_const

← Older revision		Revision as of 19:59, 17 May 2011
Line 289:		Line 289:
	This controls how many times the totem protocol will attempt to retransmit a token before giving up and forming a new configuration. If this is set, <span class="code">retransmit</span> and <span class="code">hold</span> will be calculated automatically using <span class="code">retransmits_before_loss</span> and <span class="code">token</span>.		This controls how many times the totem protocol will attempt to retransmit a token before giving up and forming a new configuration. If this is set, <span class="code">retransmit</span> and <span class="code">hold</span> will be calculated automatically using <span class="code">retransmits_before_loss</span> and <span class="code">token</span>.

	* ~~Unknown default, appears to have none (no entry in objctl)~~		* Default is <span class="code">4</span>
	* ? This must be a [http://en.wikipedia.org/wiki/Natural_number natural number]		* This must be a [http://en.wikipedia.org/wiki/Natural_number natural number]

	=== rrp_mode ===		=== rrp_mode ===

Digimer: /* clusternode's name attribute */

2011-04-28T13:58:05Z

clusternode's name attribute

← Older revision		Revision as of 13:58, 28 April 2011
Line 900:		Line 900:
	==== clusternode's name attribute ====		==== clusternode's name attribute ====

	This is the name of the cluster node. It '''~~must~~''' match the name returned by <span class="code">uname -n</span>. All other nodes must be able to connect to the node by that name. If necessary, edit your <span class="code">/etc/hosts</span> file or your [[DNS]] server to ensure that this name resolves properly. Further, the IP address returned when resolving this name will be the interface that the primary <span class="code">[[#totem; Totem Ring and the Redundant Ring Protocol\|totem]]</span> ring interface.		This is the name of the cluster node. It '''should''' match the name returned by <span class="code">uname -n</span>. All other nodes must be able to connect to the node by that name. If necessary, edit your <span class="code">/etc/hosts</span> file or your [[DNS]] server to ensure that this name resolves properly. Further, the IP address returned when resolving this name will be the interface that the primary <span class="code">[[#totem; Totem Ring and the Redundant Ring Protocol\|totem]]</span> ring interface.

	All node names '''must''' resolve to an IP address in the same network as all other nodes. If a node resolves to an IP on another network, it's totem protocol messages will not reach the other nodes and it will not be able to join the cluster. Having node names with an underscore (<span class="code">_</span>) may cause problems and are ill-advised.		All node names '''must''' resolve to an IP address in the same network as all other nodes. If a node resolves to an IP on another network, it's totem protocol messages will not reach the other nodes and it will not be able to join the cluster. Having node names with an underscore (<span class="code">_</span>) may cause problems and are ill-advised.

			The cluster will try to resolve the value here using the following methods, in order:

			# It looks up <span class="code">$HOSTNAME</span> in <span class="code">cluster.conf</span>
			# If this fails it strips the domain name from <span class="code">$HOSTNAME</span> and looks up that in <span class="code">cluster.conf</span>.
			# If this fails it looks in <span class="code">cluster.conf</span> for a fully-qualified name whose short version matches the short version of <span class="code">$HOSTNAME</span>
			# If all this fails then it will search the interfaces list for an (ipv4 only) address that matches a name in <span class="code">cluster.conf</span>.

	This attribute is required.		This attribute is required.
Line 910:		Line 917:
	* No default		* No default
	* Must match the name returned by <span class="code">uname -n</span> and must be a valid host name.		* Must match the name returned by <span class="code">uname -n</span> and must be a valid host name.

			Thanks to ''Christine Caulfield'' of [[Red Hat]] for linking to [http://people.redhat.com/ccaulfie/docs/CSNetworking.pdf her paper] that clarified this.

	==== clusternode's nodeid attribute ====		==== clusternode's nodeid attribute ====

Digimer: /* Tag; method */

2011-03-24T15:56:55Z

Tag; method

← Older revision		Revision as of 15:56, 24 March 2011
Line 1,007:		Line 1,007:
	The <span class="code"><method></span> tag supports one attribute, <span class="code">name</span>. It contains one or more <span class="code">[[#Element; device\|<device></span> tags.		The <span class="code"><method></span> tag supports one attribute, <span class="code">name</span>. It contains one or more <span class="code">[[#Element; device\|<device></span> tags.

	===== name =====		===== method's name Attribute =====

	This is a name or number meant to identify the method. It has no programmatic meaning and simply needs to be unique among the <span class="code">method</span>s for the given node.		This is a name or number meant to identify the method. It has no programmatic meaning and simply needs to be unique among the <span class="code">method</span>s for the given node.
Line 1,020:		Line 1,020:
	There is one required tag, <span class="code">name</span>, though many more attributes may be defined depending on the fence device in use. All attributes other than <span class="code">name</span> will be passed to the [[fence agent]] associated with the appropriate <span class="code">[[#Tag; fencedevice\|fencedevice]]</span>.		There is one required tag, <span class="code">name</span>, though many more attributes may be defined depending on the fence device in use. All attributes other than <span class="code">name</span> will be passed to the [[fence agent]] associated with the appropriate <span class="code">[[#Tag; fencedevice\|fencedevice]]</span>.

	====== name ======		====== device's name attribute ======

	This must match the name of the <span class="code">[[#Tag; fencedevice\|fencedevice]]</span> name.		This must match the name of the <span class="code">[[#Tag; fencedevice\|fencedevice]]</span> name.

Digimer: /* Tag; fencedevice */

2011-03-16T17:38:09Z

Tag; fencedevice

← Older revision		Revision as of 17:38, 16 March 2011
Line 1,068:		Line 1,068:
	There may be other valid attributes beyond the two listed below, depending on the [[fence agent]] being defined. Please refer to the documentation of each fence device for the extra attributes supported.		There may be other valid attributes beyond the two listed below, depending on the [[fence agent]] being defined. Please refer to the documentation of each fence device for the extra attributes supported.

	==== name ====		==== fencedevice's name attribute ====

	This is the name of the fence device. This name is searched for by the fence daemon when it decides to fence a node. As such, it must match the name given to a <span class="code">device</span> under the appropriate <span class="code">method</span> for a given node.		This is the name of the fence device. This name is searched for by the fence daemon when it decides to fence a node. As such, it must match the name given to a <span class="code">device</span> under the appropriate <span class="code">method</span> for a given node.
Line 1,075:		Line 1,075:
	* Must match the <span class="code">name</span> of a <span class="code">device</span> specified in a given <span class="code">clusternode</span>'s <span class="code">method</span>		* Must match the <span class="code">name</span> of a <span class="code">device</span> specified in a given <span class="code">clusternode</span>'s <span class="code">method</span>

	==== agent ====		==== encedevice's agent attribute ====

	This is the name of the script that <span class="code">fenced</span> will call and pass arguments to. [[Fence Agent]]s will generally be found in <span class="code">/sbin/</span> in [[RHEL]]/[[CentOS]] <span class="code">/usr/sbin/</span> in [[Fedora]].		This is the name of the script that <span class="code">fenced</span> will call and pass arguments to. [[Fence Agent]]s will generally be found in <span class="code">/sbin/</span> in [[RHEL]]/[[CentOS]] <span class="code">/usr/sbin/</span> in [[Fedora]].

Digimer: /* Tag; device */

2011-03-16T17:33:06Z

Tag; device

← Older revision		Revision as of 17:33, 16 March 2011
Line 1,016:		Line 1,016:
	===== Tag; device =====		===== Tag; device =====

	This tag tells the cluster manager which <span class="code">[[#~~Element~~; fencedevice\|fencedevice]]</span> to call in order to perform the defined fence action against the node.		This tag tells the cluster manager which <span class="code">[[#Tag; fencedevice\|fencedevice]]</span> to call in order to perform the defined fence action against the node.

	There is one required tag, <span class="code">name</span>, though many more attributes may be defined depending on the fence device in use. All attributes other than <span class="code">name</span> will be passed to the [[fence agent]] associated with the appropriate <span class="code">[[#~~Element~~; fencedevice\|fencedevice]]</span>.		There is one required tag, <span class="code">name</span>, though many more attributes may be defined depending on the fence device in use. All attributes other than <span class="code">name</span> will be passed to the [[fence agent]] associated with the appropriate <span class="code">[[#Tag; fencedevice\|fencedevice]]</span>.

	====== name ======		====== name ======

	This must match the name of the <span class="code">[[#~~Element~~; fencedevice\|fencedevice]]</span> name.		This must match the name of the <span class="code">[[#Tag; fencedevice\|fencedevice]]</span> name.

	It uses this to find out which physical (or logical) fence device to use, and in turn what fence agent to call. Any attributes beyond <span class="code">name</span> will be passed to that fence agent. Generally this includes the port the node is connected to and what action to take. In the case of single-node fence devices, like IPMI, simply the action is defined.		It uses this to find out which physical (or logical) fence device to use, and in turn what fence agent to call. Any attributes beyond <span class="code">name</span> will be passed to that fence agent. Generally this includes the port the node is connected to and what action to take. In the case of single-node fence devices, like IPMI, simply the action is defined.

Digimer: /* Tag; clusternode */

2011-03-16T00:23:43Z

Tag; clusternode

← Older revision		Revision as of 00:23, 16 March 2011
Line 922:		Line 922:
	* Must be a unique [http://en.wikipedia.org/wiki/Natural_number natural number]		* Must be a unique [http://en.wikipedia.org/wiki/Natural_number natural number]

	==== votes ====		==== clusternode's votes attribute ====

	This tells the cluster how many votes a given node contributes towards [[quorum]]. This should be set to <span class="code">1</span> unless you have a special case and understand the reasons for setting a higher value.		This tells the cluster how many votes a given node contributes towards [[quorum]]. This should be set to <span class="code">1</span> unless you have a special case and understand the reasons for setting a higher value.
Line 933:		Line 933:
	* Must be a [http://en.wikipedia.org/wiki/Natural_number natural number]		* Must be a [http://en.wikipedia.org/wiki/Natural_number natural number]

	==== weight ====		==== clusternode's weight attribute ====

	This sets the [[#dlm; The Distributed Lock Manager\|dlm]] locking weight.		This sets the [[#dlm; The Distributed Lock Manager\|dlm]] locking weight.
Line 950:		Line 950:
	At the time of this writing, totem rings will not automatically recover after a failure. Please see the note in [[#rrp_mode\|rrp_mode]] for information on how to manually recover a ring.		At the time of this writing, totem rings will not automatically recover after a failure. Please see the note in [[#rrp_mode\|rrp_mode]] for information on how to manually recover a ring.

	===== name =====		===== altname's name attribute =====

	This is the host name that resolves to the interface connected to the network that the redundant ring will communicate on. All other nodes must have their redundant ring operating on the same network.		This is the host name that resolves to the interface connected to the network that the redundant ring will communicate on. All other nodes must have their redundant ring operating on the same network.
Line 959:		Line 959:
	* Must be a host name that resolves to an IP of the interface the redundant ring will communicate on		* Must be a host name that resolves to an IP of the interface the redundant ring will communicate on

	===== port =====		===== altname's port attribute =====

	This is the port used for the redundant ring communication.		This is the port used for the redundant ring communication.
Line 968:		Line 968:
	* Must be a valid port number (<span class="code">1</span> to <span class="code">65535</span>)		* Must be a valid port number (<span class="code">1</span> to <span class="code">65535</span>)

	===== mcast =====		===== altname's mcast attribute =====

	This is the multicast address to use for the redundant ring communication.		This is the multicast address to use for the redundant ring communication.

Digimer: /* nodeid */

2011-03-15T23:49:59Z

nodeid

← Older revision		Revision as of 23:49, 15 March 2011
Line 911:		Line 911:
	* Must match the name returned by <span class="code">uname -n</span> and must be a valid host name.		* Must match the name returned by <span class="code">uname -n</span> and must be a valid host name.

	==== nodeid ====		==== clusternode's nodeid attribute ====

	This is a [http://en.wikipedia.org/wiki/Natural_number natural number] used to reference the node. It must be unique among other nodes in you cluster.		This is a [http://en.wikipedia.org/wiki/Natural_number natural number] used to reference the node. It must be unique among other nodes in you cluster.

Digimer: /* name */

2011-03-15T23:48:57Z

name

← Older revision		Revision as of 23:48, 15 March 2011
Line 898:		Line 898:
	Each node in the cluster must have it's own <span class="code"><clusternode ...></span> tag. The tag itself supports four attributes and can contain two other child-tags.		Each node in the cluster must have it's own <span class="code"><clusternode ...></span> tag. The tag itself supports four attributes and can contain two other child-tags.

	==== name ====		==== clusternode's name attribute ====

	This is the name of the cluster node. It '''must''' match the name returned by <span class="code">uname -n</span>. All other nodes must be able to connect to the node by that name. If necessary, edit your <span class="code">/etc/hosts</span> file or your [[DNS]] server to ensure that this name resolves properly. Further, the IP address returned when resolving this name will be the interface that the primary <span class="code">[[#totem; Totem Ring and the Redundant Ring Protocol\|totem]]</span> ring interface.		This is the name of the cluster node. It '''must''' match the name returned by <span class="code">uname -n</span>. All other nodes must be able to connect to the node by that name. If necessary, edit your <span class="code">/etc/hosts</span> file or your [[DNS]] server to ensure that this name resolves properly. Further, the IP address returned when resolving this name will be the interface that the primary <span class="code">[[#totem; Totem Ring and the Redundant Ring Protocol\|totem]]</span> ring interface.

Digimer at 23:47, 15 March 2011

2011-03-15T23:47:08Z

← Older revision		Revision as of 23:47, 15 March 2011
Line 9:		Line 9:
	This is the [[RHCS]] "Stable 2" version of the <span class="code">cluster.conf</span> document. It started life as a clone of the "Stable 3" document, and may contain traces of options and values not available in Stable 2. Once I feel that this document is accurate, I will remove these warnings.		This is the [[RHCS]] "Stable 2" version of the <span class="code">cluster.conf</span> document. It started life as a clone of the "Stable 3" document, and may contain traces of options and values not available in Stable 2. Once I feel that this document is accurate, I will remove these warnings.

	'''Warning''': I screwed up the names of some syntax. Anything in '<span class="code"><...></span>' is a tag, not an element. An element is the data contained between an opening and closing tag.		'''Warning''': I screwed up the names of some syntax. Anything in <span class="code"><...></span> is a tag, not an element. An element is the data contained between an opening and closing tag. Further, I may have screwed up other syntax, I will need to check. Officially though, any <span class="code"><foo var="val"></span> variable/value pair is an attribute.

	= Format =		= Format =