search for: o2cb_heartbeat_mode

Displaying 3 results from an estimated 3 matches for "o2cb_heartbeat_mode".

2009 Nov 13
1
Cannot set heartbeat dead threshold
...S: 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...
2010 May 31
2
O2CB_HEARTBEAT_THRESHOLD won't take changes
Hello All, I have multiple OCFS2 clusters on SLES10 SP2 running Xen. We needed to increase the O2CB_HEARTBEAT_THRESHOLD from 31 up to 61 and did so successfully on 2 of our 3 clusters. However on one of the three clusters we are not able to change the value. The /etc/sysconfig/o2cb file contains 61 as the threshold after reconfiguring via /etc/init.d/o2cb configure, we reconfigure all 3 nodes at
2010 Jan 18
1
Getting Closer (was: Fencing options)
...t;>> # O2CB_KEEPALIVE_DELAY_MS: Max time in ms before a keepalive packet is >>> sent >>> O2CB_KEEPALIVE_DELAY_MS= >>> >>> # O2CB_RECONNECT_DELAY_MS: Min time in ms between connection attempts >>> O2CB_RECONNECT_DELAY_MS= >>> >>> # 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" >>> >>> _______________________________________________ >>> Ocfs2-...