Ocfs2 users - Nov 2009 - Cannot set heartbeat dead threshold

Hi

I have:
SLES 10 SP2 (2.6.16.60-0.21-smp)
ocfs2-tools-1.4.0-0.3
ocfs2console-1.4.0-0.3

and I can't change "heartbeat dead threshold" value.

Content of /etc/sysconfig/o2cb:

# O2CB_ENABLED: 'true' means to load the driver on boot.
O2CB_ENABLED=true

# O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start.
O2CB_BOOTCLUSTER=ocfs2

# O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead.
O2CB_HEARTBEAT_THRESHOLD=151

# O2CB_IDLE_TIMEOUT_MS: Time in ms before a network connection is  
considered dead.
O2CB_IDLE_TIMEOUT_MS=10000

# O2CB_KEEPALIVE_DELAY_MS: Max time in ms before a keepalive packet is sent
O2CB_KEEPALIVE_DELAY_MS=5000

# O2CB_RECONNECT_DELAY_MS: Min time in ms between connection attempts
O2CB_RECONNECT_DELAY_MS=2000

# O2CB_HEARTBEAT_MODE: Whether to use the native "kernel" or the
"user"
# driven heartbeat (for example, for integration with heartbeat 2.0.x)
O2CB_HEARTBEAT_MODE="kernel"


so, O2CB_HEARTBEAT_THRESHOLD is 151.

Then I have restart service o2cb or even reboot server and...:

# service o2cb status
Module "configfs": Loaded
Filesystem "configfs": Mounted
Module "ocfs2_nodemanager": Loaded
Module "ocfs2_dlm": Loaded
Module "ocfs2_dlmfs": Loaded
Filesystem "ocfs2_dlmfs": Mounted
Checking O2CB cluster ocfs2: Online
Heartbeat dead threshold = 31
Network idle timeout: 10000
Network keepalive delay: 5000
Network reconnect delay: 2000
Checking O2CB heartbeat: Not active

so, Heartbeat dead threshold is 31!!!

ok. I'll try use configure...

# service o2cb configure

Load O2CB driver on boot (y/n) [y]:
Cluster to start on boot (Enter "none" to clear) [ocfs2]:
Specify heartbeat dead threshold (>=7) [151]: 151
Specify network idle timeout in ms (>=5000) [10000]:
Specify network keepalive delay in ms (>=1000) [5000]:
Specify network reconnect delay in ms (>=2000) [2000]:
Use user-space driven heartbeat? (y/n) [n]:
Writing O2CB configuration: OK
O2CB cluster ocfs2 already online

so, we see that "Specify heartbeat dead threshold" get my current
value
(151) from /etc/sysconfig/o2cb.

but again we have:
# service o2cb status
...
Heartbeat dead threshold = 31
...

trying check file from configfs:
# cat /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
31

# echo 151 > /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
# cat /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
31

# ls -l /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
-rw-r--r-- 1 root root 4096 2009-11-13 17:42  
/sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold

what's a problem?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://oss.oracle.com/pipermail/ocfs2-users/attachments/20091113/c36d25e7/attachment-0001.html

Ping Novell Support. The base code works fine. This could be a bug in
sles10 sp2.

voinovpa at gmail.com wrote:
> Hi
>
> I have:
> SLES 10 SP2 (2.6.16.60-0.21-smp)
> ocfs2-tools-1.4.0-0.3
> ocfs2console-1.4.0-0.3
>
> and I can't change "heartbeat dead threshold" value.
>
> Content of /etc/sysconfig/o2cb:
>
> # O2CB_ENABLED: 'true' means to load the driver on boot.
> O2CB_ENABLED=true
>
> # O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start.
> O2CB_BOOTCLUSTER=ocfs2
>
> # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead.
> O2CB_HEARTBEAT_THRESHOLD=151
>
> # O2CB_IDLE_TIMEOUT_MS: Time in ms before a network connection is 
> considered dead.
> O2CB_IDLE_TIMEOUT_MS=10000
>
> # O2CB_KEEPALIVE_DELAY_MS: Max time in ms before a keepalive packet is 
> sent
> O2CB_KEEPALIVE_DELAY_MS=5000
>
> # O2CB_RECONNECT_DELAY_MS: Min time in ms between connection attempts
> O2CB_RECONNECT_DELAY_MS=2000
>
> # O2CB_HEARTBEAT_MODE: Whether to use the native "kernel" or the
"user"
> # driven heartbeat (for example, for integration with heartbeat 2.0.x)
> O2CB_HEARTBEAT_MODE="kernel"
>
>
> so, O2CB_HEARTBEAT_THRESHOLD is 151.
>
> Then I have restart service o2cb or even reboot server and...:
>
> # service o2cb status
> Module "configfs": Loaded
> Filesystem "configfs": Mounted
> Module "ocfs2_nodemanager": Loaded
> Module "ocfs2_dlm": Loaded
> Module "ocfs2_dlmfs": Loaded
> Filesystem "ocfs2_dlmfs": Mounted
> Checking O2CB cluster ocfs2: Online
> Heartbeat dead threshold = 31
> Network idle timeout: 10000
> Network keepalive delay: 5000
> Network reconnect delay: 2000
> Checking O2CB heartbeat: Not active
>
> so, Heartbeat dead threshold is 31!!!
>
> ok. I'll try use configure...
>
> # service o2cb configure
>
> Load O2CB driver on boot (y/n) [y]:
> Cluster to start on boot (Enter "none" to clear) [ocfs2]:
> Specify heartbeat dead threshold (>=7) [151]: 151
> Specify network idle timeout in ms (>=5000) [10000]:
> Specify network keepalive delay in ms (>=1000) [5000]:
> Specify network reconnect delay in ms (>=2000) [2000]:
> Use user-space driven heartbeat? (y/n) [n]:
> Writing O2CB configuration: OK
> O2CB cluster ocfs2 already online
>
> so, we see that "Specify heartbeat dead threshold" get my current
> value (151) from /etc/sysconfig/o2cb.
>
> but again we have:
> # service o2cb status
> ...
> Heartbeat dead threshold = 31
> ...
>
> trying check file from configfs:
> # cat /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
> 31
>
> # echo 151 > /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
> # cat /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
> 31
>
> # ls -l /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
> -rw-r--r-- 1 root root 4096 2009-11-13 17:42 
> /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
>
> what's a problem?
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-users