search for: o2cb_heartbeat_threshold

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 the same time after...

...cfs2console-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 # O2...

...xx o2cb: # 'dpkg-reconfigure ocfs2-tools'. # # O2CB_ENABLED: 'true' means to load the driver on boot. O2CB_ENABLED=true # O2CB_STACK: The name of the cluster stack backing O2CB. O2CB_STACK=o2cb # O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start. O2CB_BOOTCLUSTER=xx #O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead. O2CB_HEARTBEAT_THRESHOLD= # O2CB_IDLE_TIMEOUT_MS: Time in ms before a network connection is considered dead. O2CB_IDLE_TIMEOUT_MS= # O2CB_KEEPALIVE_DELAY_MS: Max time in ms before a keepalive packet is sent O2CB_KEEPALIVE_DELAY_MS= # O2CB_RECONNECT_DELA...

Dear Sirs and Madams, I run a small visual effects production company, Hammerhead Productions. We'd like to have an easily extensible inexpensive relatively high-performance storage network using open-source components. I was hoping that OCFS2 would be that system. I have a half-dozen 2 TB fileservers I'd like the rest of the network to see as a single 12 TB disk, with the aggregate

...on the sending side) > were pretty generic. > > What we've done so far: > > - Mount options: ?added nointr, noatime, datavolume ? (removed "defaults") > - Multipath.conf: added it (we were running without a multipath.conf > which means use all dm- defaults) > - O2CB_HEARTBEAT_THRESHOLD: set it to 76 (was running default of 31) > - Turned on netconsole (but it's not telling us anything useful yet) > > I know Sunil suggested that we can get to the bottom of the fencing > once and for all with the logging, but the above set of changes were > "best practice&qu...

Hi to all, this is My first time on this mailinglist. I have a problem with Ocfs2 on Debian etch 4.0 I'd like when a node go down or freeze without unmount the ocfs2 partition the heartbeat not fence the server that work well ( kernel panic ). I'd like disable or heartbeat or fencing. So we can work also with only 1 node. Thanks

...nning # 'dpkg-reconfigure ocfs2-tools'. # # O2CB_ENABLED: 'true' means to load the driver on boot. O2CB_ENABLED=true # O2CB_STACK: The name of the cluster stack backing O2CB. O2CB_STACK=o2cb # O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start. O2CB_BOOTCLUSTER=pbx # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead. O2CB_HEARTBEAT_THRESHOLD= # O2CB_IDLE_TIMEOUT_MS: Time in ms before a network connection is considered dead. O2CB_IDLE_TIMEOUT_MS= # O2CB_KEEPALIVE_DELAY_MS: Max time in ms before a keepalive packet is sent O2CB_KEEPALIVE_DELAY_MS= # O2CB_RECONNE...

Hello, I have two nodes running the 2.6.9-22.0.2.ELsmp kernel and the OCFS2 1.2.1 RPMs. About once a week, one of the nodes crashes itself (self- fencing) and I get a full vmcore on my netdump server. The netdump log file shows the shared filesystem LUN (/dev/dm-6) did not respond within 12000ms. I have not changed the default heartbeat values in /etc/sysconfig/o2cb. There was no other IO

...lower-test I've also tried with an ext3 filesystem on the drbd device in primary/secondary configuration, this worked fine. So this only happens when the datadir is on a ocfs2 file system. Some more facts: - still the same error if filesystem is unmounted on the other machine of the cluster - O2CB_HEARTBEAT_THRESHOLD=31 - Ubuntu 8.043 - MySQL server is mysql-server 5.0.51a - ocfs2-tools 1.3.9 - drbd8-utils 2:8.0.11-0 Has anybody experienced a similar problem? May it have to do with locking or extended attributes? I've also asked on the Mysql users side as I do not know whether this is an OCFS or a MySQL pr...

...# 'dpkg-reconfigure ocfs2-tools'. # # O2CB_ENABLED: 'true' means to load the driver on boot. O2CB_ENABLED=true # O2CB_STACK: The name of the cluster stack backing O2CB. O2CB_STACK=pcmk # O2CB_BOOTCLUSTER: If not empty, the name of a cluster to start. O2CB_BOOTCLUSTER=pacemaker # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead. O2CB_HEARTBEAT_THRESHOLD= # O2CB_IDLE_TIMEOUT_MS: Time in ms before a network connection is considered dead. O2CB_IDLE_TIMEOUT_MS= # O2CB_KEEPALIVE_DELAY_MS: Max time in ms before a keepalive packet is sent O2CB_KEEPALIVE_DELAY_MS= # O2CB_RECONNECT_...

...erprise Linux AS-up (2.6.9-34.EL) root (hd0,0) kernel /vmlinuz-2.6.9-34.EL ro root=/dev/VolGroup00/LogVol00 elevator=deadline vga=0xf05 initrd /initrd-2.6.9-34.EL.img [root at rac1 ~]# --- [root at rac1 ~]# cat /etc/sysconfig/o2cb O2CB_ENABLED=true O2CB_BOOTCLUSTER=ocfs2 O2CB_HEARTBEAT_THRESHOLD=16 [root at rac1 ~]# --- Crash message: --- Apr 18 15:54:43 rac1/rac1 (2858,1):o2net_set_nn_state:426 accepted connection from node rac2 (num 1) at 10.0.1.2:7777 Apr 18 15:54:47 rac1/rac1 (2858,1):__dlm_print_nodes:384 Nodes in my domain ("CA641AEC0417495BA7302FC14F6F99B7"): Apr 18 15...

...w some other people is getting on a similar trouble (http://www.mail-archive.com/ocfs2-users@oss.oracle.com/msg01135.html) but the thread don't gave me help... Anyone has any idea? Thanks you in advance. Maurizio web-ha1:~ # cat /etc/sysconfig/o2cb O2CB_ENABLED=true O2CB_BOOTCLUSTER=ocfs2 O2CB_HEARTBEAT_THRESHOLD=451 web-ha1:~ # web-ha1:~ # cat /etc/ocfs2/cluster.conf node: ip_port = 7777 ip_address = 192.168.255.1 number = 0 name = web-ha1 cluster = ocfs2 node: ip_port = 7777 ip_address = 192.168.255.2 number = 1 name = web-ha2...

Hello all, are there any issues concerning ocfs2 (v 1.2.3) and device-mapper-multipath-0.4.5-12.0.RHEL4? I've build a 4 node cluster with two ocfs2 mounts on /dev/dm-0 and /dev/dm-1. Under heavy load the nodes dies after about two minutes reproducably ;-(( Once I've loaded the ocfs2 modules it seems to me that both modules (device-mapper-multipath related as well as ocfs related) are

...should initiate an failover to the second controller. this works, of only one clustermember is active for ocfs. At the moment there are two clustermembers, at least one crashes often both clients does a reboot. The the timeouts are the following O2CB_ENABLED=true O2CB_BOOTCLUSTER=debianocfs O2CB_HEARTBEAT_THRESHOLD=61 O2CB_IDLE_TIMEOUT_MS=90000 O2CB_KEEPALIVE_DELAY_MS=2000 O2CB_RECONNECT_DELAY_MS=2000 in the attachment i have the Dell multipath.conf. failback is already to manual, so it does least controller switches. what could be the reason for the crashes? best regards thomas -------------- nex...

I am trying to mount the same partition from a KVM ubuntu 8.04.1 virtual machine and on an ubuntu 8.04.1 host server. I am able to mount the partition just on fine on two ubuntu host servers, they both talk to each other. The logs on both servers show the other machine mounting and unmounting the drive. However, when I mount the drive in the KVM VM I get no communication to the host

We're trying to setup a dual-primary DRBD environment, with a shared disk with either OCFS2 or GFS. The environment is a Centos 5.3 with DRBD82 (but also tried with DRBD83 from testing) . Setting up a single primary disk and running bonnie++ on it works. Setting up a dual-primary disk, only mounting it on one node (ext3) and running bonnie++ works When setting up ocfs2 on the /dev/drbd0

We're trying to setup a dual-primary DRBD environment, with a shared disk with either OCFS2 or GFS. The environment is a Centos 5.3 with DRBD82 (but also tried with DRBD83 from testing) . Setting up a single primary disk and running bonnie++ on it works. Setting up a dual-primary disk, only mounting it on one node (ext3) and running bonnie++ works When setting up ocfs2 on the /dev/drbd0

...n their own) in order to get the cluster back. The would not unmount the file system, so we hard-panic'd (insmod panic.ko). Vitals: - Linux mgr01 2.6.18-164.2.1.el5 #1 SMP Wed Sep 30 12:52:46 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux - ocfs2-2.6.18-164.2.1.el5-1.4.4-1.el5 - MD3000i iSCSI - O2CB_HEARTBEAT_THRESHOLD=61 - O2CB_IDLE_TIMEOUT_MS=30000 - O2CB_KEEPALIVE_DELAY_MS=2000 - O2CB_RECONNECT_DELAY_MS=2000 - iSCSI node.session.timeo.replacement_timeout = 120 - iSCSI node.conn[0].timeo.noop_out_interval = 5 - node.conn[0].timeo.noop_out_timeout = 5 Logs at the time of failure on mgr01: Nov 6 01:00:12...

Two questions (and then a bonus one), kind of interrelated, but, first, some basic info. I'm using OCFS2 on OpenSUSE 10.2, kernel 2.6.18.8(-0.7). There are three nodes in the OCFS2 cluster, backed by Openfiler iSCSI storage. First, I'm using Openfiler and iSCSI volumes to back my OCFS2 file system. The nodes that are part of the OCFS2 cluster use the file system as a shared storage

Hi, everyone I have some questions with the OCFS2 when using it as vm-store. With Ubuntu 1204, kernel version is 3.2.40, and ocfs2-tools version is 1.6.4. As the network configure change, there are some issues as the log below. Why is there the information of "Node 255 (he) is the Recovery Master for the dead node 255" in the syslog? Why the host ZHJD-VM6 is blocked until it reboot