Christopher Duncan
2005-Oct-11 16:30 UTC
[Ocfs2-users] fencing timeout- increasing min time
What would the dangers/issues be within increasing the minimum time before the fencing enforced panic of a node? We're hitting problems where HBA multipath failover does not happen fast enough and we may need to up the fencing timeout to something closer to 30-60 secs or more. Is this mostly a performance impact or does it increase the window for corruption issues? Looks like from the current code the min timeout is 4 secs. For hardware/software details we're using CentOS4.1 x86_64 (clone of RedHat 4.1), on a cluster of Sun v20z's, Opteron 250s. The cards involved are Emulex and multipath is mdadm based.
Maybe Matching Threads
- XEN HA Cluster with LVM fencing and live migration ? The right way ?
- Getting Closer (was: Fencing options)
- has anyone experienced problems with ocfs2 1.2.5-1 using Emulex LP10000 HBA cards and EMC CX700 SAN's?
- pcifront (CONFIG_XEN_PCIDEV_FRONTEND=m) support in RHEL 4.5 x86 Dom U
- CentOS-4 RC1 (i386) Bugfixes