Red Hat Cluster Suite Overview

Used For
Dispatching Web Traffic

High-availability clusters (Failover Clusters)
When any node fails the cluster automatically fail-over services from the node down
to another.
High-availability clusters exist to keep the overall services of the cluster
available as much as take into account the fallibility of computing
hardware and software. As the primary node in a high-availability cluster fails, it
is replaced by a secondary node that has been waiting for that moment. That
secondary node is usually a mirror image of the primary node, so that when it does replace
the primary, it can completely take over its identity and thus keep the system environment
consistent from the user’s point of view.
With each of those three basic types of clusters, hybrids and interbreeding
often occur between them. Thus you can find a high-availability cluster that can
also load-balance users across its nodes, while still attempting to maintain a degree of high-
availability. Similarly, you can find a parallel cluster that can also perform load balancing
between the nodes separately from what was programmed into the application. Although
the clustering system itself is independent of what software or hardware is in use, hardware
connections play a pivotal role when it comes to running the system efficiently

– Avoid downtime of services

– Avoid single point of failure

– Always with redundancy

– Almost all load balancing cluster are with HA capability

Cont. High Availability :

Used for
1- Databases
2- Fileserver
The need for High Availability Cluster (HA)
– Cost per Minute for downtime

Leave a Reply