[Ocfs2-users] Default Values of heartbeat dead threshold

[Schmitter, Martin]

Hi Devender,

this is a very complex question.

Timeouts must be set in conjunction with your infrastructure.

What type of storage? What OCFS2 Version? Etc. The major problem is, to synchronies the timeouts with CRS timeouts to prevent different decisions. In fact, I am pretty sure, you won’t get a default value ore suggestion.

In general you have to do a lot of tests!

Good praxis for me:
Heartbeat dead threshold =  around 61
network idle timeout = around 70000
network keepalive delay in ms 5000
network reconnect delay in ms 5000

in a multipath environment with a virtual san.

As I already mentioned timeouts have to be set in conjunction with your infrastructure and san system. This can be totally different for your needs. Do not take OCFS2 with CRS easy. This is very difficult and make sure you are using the latest releases.

Everything without warranty! Good Luck

Regards

Martin 
________________________________________
Von: ocfs2-users-bounces at oss.oracle.com [ocfs2-users-bounces at oss.oracle.com] im Auftrag von Devender Narula [devendernarula at yahoo.com]
Gesendet: Freitag, 5. Juni 2009 12:59
An: ocfs2-users at oss.oracle.com
Betreff: [Ocfs2-users] Default Values of heartbeat dead threshold

Hi Guys

i got two node RAC cluster Running on RHEL 5.0 .. i just want to what is oracle recomendid Defaults values for below mention parameters

Thanks for your help

Heartbeat dead threshold
network idle timeout
network keepalive delay in ms
network reconnect delay in ms
kernel.panic_on_oops
kernel.panic

Regards,

Devender





_______________________________________________
Ocfs2-users mailing list
Ocfs2-users at oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users