High-availability cluster

High-availability clusters (also known as HA clusters, fail-over clusters) are groups of <a href="/facts/Computer/SQe1aK05">computers</a> that support <a href="/facts/Server_(computing)/dEaYFD7r">server</a> <a href="/facts/Application_software/YQuj7Kog">applications</a> that can be reliably utilized with <a href="/facts/High_availability/y3J8GnEo">a minimum amount of down-time</a>. They operate by using <a href="/facts/High_availability_software/HbSU3tJ0">high availability software</a> to harness <a href="/facts/Redundancy_(engineering)/odqzTmIo">redundant</a> computers in groups or <a href="/facts/Computer_cluster/mT7S1BcX">clusters</a> that provide continued service when system components fail. Without clustering, if a server running a particular application crashes, the application will be unavailable until the crashed server is fixed. HA clustering remedies this situation by detecting hardware/software faults, and immediately restarting the application on another system without requiring administrative intervention, a process known as <a href="/facts/Failover/Lw0rXfv9">failover</a>. As part of this process, clustering software may configure the node before starting the application on it. For example, appropriate file systems may need to be imported and mounted, network hardware may have to be configured, and some supporting applications may need to be running as well.
HA clusters are often used for critical <a href="/facts/Database_management_system/VYcpkevb">databases</a>, file sharing on a network, business applications, and customer services such as <a href="/facts/Electronic_commerce/7vxeea0Y">electronic commerce</a> <a href="/facts/Websites/SAsjJnca">websites</a>.
HA cluster implementations attempt to build redundancy into a cluster to eliminate single points of failure, including multiple network connections and data storage which is redundantly connected via <a href="/facts/Storage_area_network/e7bmhrmB">storage area networks</a>.
HA clusters usually use a <a href="/facts/Heartbeat_(computing)/b8fgB0JJ">heartbeat</a> private network connection which is used to monitor the health and status of each node in the cluster. One subtle but serious condition all clustering software must be able to handle is <a href="/facts/Split-brain_(computing)/olHWjQLT">split-brain</a>, which occurs when all of the private links go down simultaneously, but the cluster nodes are still running. If that happens, each node in the cluster may mistakenly decide that every other node has gone down and attempt to start services that other nodes are still running. Having duplicate instances of services may cause data corruption on the shared storage.
HA clusters often also use <a href="/facts/Quorum_(distributed_computing)/gS6d6aPN">quorum</a> witness storage (local or cloud) to avoid this scenario. A witness device cannot be shared between two halves of a split cluster, so in the event that all cluster members cannot communicate with each other (e.g., failed heartbeat), if a member cannot access the witness, it cannot become active.

High-availability cluster open-in-new

High-availability cluster