- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Redhat 6.1 Cluster Active/Active
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2012 08:25 AM
11-25-2012 08:25 AM
Redhat 6.1 Cluster Active/Active
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2012 10:43 AM
11-25-2012 10:43 AM
Re: Redhat 6.1 Cluster Active/Active
In a RedHat Cluster, a quorum partition is technically always optional. However, a two-node cluster without a quorum partition may behave badly if the heartbeat connection fails between the nodes: if the chosen fencing mechanism allows the fenced node to reboot, it will then re-establish cluster on its own and fence the other node if the heartbeat connection is still failing. This will cause a see-saw effect until the heartbeat connection is fixed or the admin stops the useless behaviour.
Please see this RedHat tech brief:
How to Optimally Configure a Quorum Disk in Red Hat Enterprise Linux Clustering and High-Availability Environments
https://access.redhat.com/knowledge/articles/216443