1/etc/sysconfig/o2cb(5)        OCFS2 Manual Pages        /etc/sysconfig/o2cb(5)
2
3
4

NAME

6       /etc/sysconfig/o2cb  -  Cluster configuration file for the o2cb cluster
7       stack.
8

SYNOPSIS

10       The configuration file /etc/sysconfig/o2cb stores  the  active  cluster
11       stack,  its  name and the various cluster timeouts for the o2cb cluster
12       stack.
13
14

DESCRIPTION

16       This file can be populated using the o2cb init script.  An  example  of
17       the same is illustrated in the examples section.
18
19       The list of configurable parameters in this file are:
20
21
22       O2CB_STACK
23              Name  of  the  cluster stack. The possible values are o2cb, pcmk
24              and cman.  o2cb is the default cluster stack of the  OCFS2  file
25              system.  pcmk (Pacemaker) and cman (rgmanager) are the two other
26              cluster stacks that are supported by the same file system.
27
28
29       O2CB_BOOTCLUSTER
30              Name of the active cluster.  While  /etc/ocfs2/cluster.conf  can
31              hold  descriptions  of multiple clusters, only one can be active
32              at any one time. The name of that active  cluster  is  specified
33              here.  The  name  itself  can be upto 16 alphanumeric characters
34              [0-9A-Za-z] with no special characters.
35
36       The remaining configurable parameters (cluster timeouts) are only rele‐
37       vant for the o2cb cluster stack. These cluster timeouts are used by the
38       o2cb cluster stack to determine whether a node is dead  or  alive.  The
39       default  timeouts are just a guide and may need to be tweaked depending
40       on the hardware the software is running on.
41
42       The various cluster timeouts for the o2cb cluster stack are:
43
44       O2CB_HEARTBEAT_THRESHOLD
45              The disk heartbeat timeout is the number of  two  second  itera‐
46              tions  before  a node is considered dead. The exact formula used
47              to convert the timeout in seconds to the number of iterations is
48              as follows:
49
50                  O2CB_HEARTBEAT_THRESHOLD = (((timeout in seconds) / 2) + 1)
51
52              For  example, to specify a 60 sec timeout, set it to 31. For 120
53              secs, set it to 61.  The default for this  timeout  is  60  secs
54              (O2CB_HEARTBEAT_THRESHOLD = 31).
55
56              While  it  defaults to 60 secs, multipath users typically set it
57              to 120 secs.
58
59
60       O2CB_IDLE_TIMEOUT_MS
61              The network idle timeout  specifies  the  time  in  milliseconds
62              before  a  network  connection  is  considered  dead.  While  it
63              defaults to 30000 ms, network bonding users typically set it  to
64              60000 ms.
65
66
67       O2CB_KEEPALIVE_DELAY_MS
68              The  network  keepalive specifies the maximum delay in millisec‐
69              onds before a keepalive packet is sent to another node to  check
70              whether it is alive or not. It defaults to 2000 ms.
71
72
73       O2CB_RECONNECT_DELAY_MS
74              The  network  reconnect specifies the minimum delay in millisec‐
75              onds between repeated connect attempts. It defaults to 2000 ms.
76

EXAMPLE

78       The example below illustrates populating the o2cb sysconfig file  using
79       the o2cb init script.
80
81
82       $ service o2cb configure
83       Configuring the O2CB driver.
84
85       This will configure the on-boot properties of the O2CB driver.
86       The following questions will determine whether the driver is loaded on
87       boot.  The current values will be shown in brackets ('[]').  Hitting
88       <ENTER> without typing an answer will keep that current value.  Ctrl-C
89       will abort.
90
91       Load O2CB driver on boot (y/n) [n]: y
92       Cluster stack backing O2CB [o2cb]:
93       Cluster to start on boot (Enter "none" to clear) [ocfs2]: webcluster
94       Specify heartbeat dead threshold (>=7) [31]: 62
95       Specify network idle timeout in ms (>=5000) [30000]: 60000
96       Specify network keepalive delay in ms (>=1000) [2000]:
97       Specify network reconnect delay in ms (>=2000) [2000]:
98       Writing O2CB configuration: OK
99
100
101       $ cat /etc/sysconfig/o2cb
102       #
103       # This is a configuration file for automatic startup of the O2CB
104       # driver.  It is generated by running /etc/init.d/o2cb configure.
105       # On Debian based systems the preferred method is running
106       # 'dpkg-reconfigure ocfs2-tools'.
107       #
108
109       # O2CB_ENABLED: 'true' means to load the driver on boot.
110       O2CB_ENABLED=true
111
112       # O2CB_STACK: The name of the cluster stack backing O2CB.
113       O2CB_STACK=o2cb
114
115       # O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start.
116       O2CB_BOOTCLUSTER=webcluster
117
118       # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead.
119       O2CB_HEARTBEAT_THRESHOLD=62
120
121       # O2CB_IDLE_TIMEOUT_MS: Time in ms before a network connection is considered dead.
122       O2CB_IDLE_TIMEOUT_MS=60000
123
124       # O2CB_KEEPALIVE_DELAY_MS: Max time in ms before a keepalive packet is sent
125       O2CB_KEEPALIVE_DELAY_MS=2000
126
127       # O2CB_RECONNECT_DELAY_MS: Min time in ms between connection attempts
128       O2CB_RECONNECT_DELAY_MS=2000
129
130

SEE ALSO

132       o2cb(7) o2cb(8) ocfs2.cluster.conf(5)
133
134

AUTHORS

136       Oracle Corporation
137
138
140       Copyright © 2004, 2012 Oracle. All rights reserved.
141
142
143
144Version 1.8.5                    January 2012           /etc/sysconfig/o2cb(5)
Impressum