[Ocfs2-users] O2CB_HEARTBEAT_THRESHOLD won't take changes

[Tao Ma]

Elliott Perrin wrote:
> Hello Tao,
>
>   
>> Hi Elliott,
>> Elliott Perrin wrote:
>>     
>>> 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 unmounting the volume and stopping ocfs2
>>> and o2cb on all nodes in the cluster but on restart the value is
>>>       
>> reset
>>     
>>> to 31. We have even gone so far as to change the default value in the
>>> /etc/init.d/o2cb script from 31 to 61 thinking that must be where the
>>> setting of 31 is coming from and even then, the value is set back to
>>> 31. Oh, and yes, we have rebooted with the new values in both the
>>> /etc/sysconfig/o2cb config and with our change of the default value
>>>       
>> in
>>     
>>> /etc/init.d/o2cb with no luck.
>>>
>>>       
>> I would deem that you said that
>> /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold can't be set
>> to 61, right?
>>     
>
> Yes that is correct. 
>
>   
>> You said even with restart, the heartbeat threadshold is still 31? That
>> would be too strange.
>>     
>
> I thought the same as well. 
>
>   
>> So could you please do the following steps:
>> 1. /etc/init.d/o2cb offline
>> this will make the cluster offline. Please make sure you didn't see
>> anything in /sys/kernel/config/cluster/.
>>     
>
> That folder did disappear during restart but I am not sure if the admin I was working with did an offline or a stop. We will do an offline during scheduled maintenance tomorrow. 
>   
IIRC, stop only works if you set up o2cb enabled(You set this when do 
/etc/init.d/o2cb configure and in the option"Load O2CB driver on boot 
(y/n)" .)
So if you don't have it enabled, stop does nothing.
>   
>> 2.  grep HEARTBEAT /etc/sysconfig/o2cb and paste here so that we know
>> the configuration file has been changed.
>>     
>
> elliott.perrin at XXXXXXXXXXXX:~> grep HEART /etc/sysconfig/o2cb
> # O2CB_HEARTBEAT_THRESHOLD: Iterations before a node is considered dead.
> O2CB_HEARTBEAT_THRESHOLD=61
> # O2CB_HEARTBEAT_MODE: Whether to use the native "kernel" or the "user"
> O2CB_HEARTBEAT_MODE="kernel"
>   
yeah, so the configuration is right.
>   
>> 3. strace /etc/init.d/o2cb online and attach the output here. let's see
>> what's going on.
>> 4. cat /sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold to see
>> the new value.
>>     
>
> elliott.perrin at XXXXXXXXXXX:~> cat /sys/kernel/config/cluster/XXXXXXX/heartbeat/dead_threshold
> 31
>   
oh...
> Thank you Tao, we will be performing maintenance on this cluster in the next couple days and will try these steps. 
>   
np. Let us wait and see what's wrong.

Regards,
Tao