Red Hat GFS 5.2.1 -, Руководство администратора

Страница: 57 / 192

Chapter 6. Creating the Cluster Configuration System Files 43
Note
Two commonly used optional
cluster.ccs
parameters are included in this procedure. For a descrip-
tion of other optional parameters, refer to the
lock_gulmd(5)
man page.
cluster {
name = " ClusterName "
lock_gulm {
servers = [" NodeName ",..., " NodeName "]
heartbeat_rate = Seconds <--
Optional
allowed_misses = Number <--
Optional
}
}
Figure 6-1. File Structure:
cluster.ccs
Parameter Description
ClusterName
The name of the cluster, from 1 to 16 characters long.
NodeName
The name of each node that runs the LOCK_GULM server. Each node
name must appear under
nodes.ccs:nodes
.
Seconds
(Optional) For
heartbeat_rate
, the rate at which the heartbeats are checked by
the server in seconds. Two-thirds of this time is the rate at which the
heartbeats are sent. The default values is 15.
Number
(Optional) For
allowed_misses
, How many consecutive heartbeats can be missed
before a node is marked as expired. The default value is 2.
Table 6-1. File Syntax Description: Variables for
cluster.ccs
cluster {
name = "alpha"
lock_gulm {
servers = ["n01", "n02", "n03"]
heartbeat_rate = 21
allowed_misses = 3
}
}
Example 6-2.
cluster.ccs
6.7. Creating the
fence.ccs
File
You can configure each node in a GFS cluster for a variety of fencing devices. To configure fencing
for a node, you need to perform the following tasks:
•
Create the
fence.ccs
file — Define the fencing devices available in the cluster (described in this
section).
•
Create the
nodes.ccs
file — Define which fencing method (or methods) each node should use
(refer to Section 6.8 Creating the
nodes.ccs
File ).