High CPU or I/O load on cluster node causes fencing with Red Hat Enterprise Linux cluster and default totem settings
Issue
- High CPU or I/O load on cluster node causes fencing in Red Hat High Availability Cluster
- My cluster nodes are getting fenced when they become unresponsive due to high load. Can I make the cluster less sensitive to this issue?
- System performance issue on production cluster setup. Sometime, cluster node just goes hang or get rebooted. It's been observed that our production Application Cluster is not performing properly. The incidences are happening like VM reboot on peak hours followed by fencing and we have observed a high load/iowait and performance degradation before the reboot. How can we recover from this situation?
- Linux cluster nodes rebooted automatically, cluster node got rebooted and we want to investigate the possible reason for it.
Environment
- Red Hat Enterprise Linux Server 5 (with the High Availability or Resilient Storage Add Ons)
- Red Hat Enterprise Linux Server 6 (with the High Availability or Resilient Storage Add Ons)
- Periods of high CPU or I/O utilization
- Default TOTEM settings in
/etc/cluster/cluster.conf
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.