1. Introduction to Oracle Solaris Cluster
2. Key Concepts for Oracle Solaris Cluster
Features and Benefits of a Zone Cluster
Cluster Configuration Repository
Shared Devices, Local Devices, and Device Groups
How Oracle Solaris Cluster Uses Shared Devices
Description of a Resource Type
Description of a Resource Group
Description of a Failover Data Service
Description of a Scalable Data Service
Description of a Parallel Application
Visualization of System Resource Usage
The purpose of failfast is to halt a component that is not healthy enough to continue correct operations. Oracle Solaris Cluster software includes many failfast mechanisms that detect different unhealthy conditions.
If the Oracle Solaris Cluster system detects a critical failure on the global-cluster voting node, the system forcibly shuts down the Oracle Solaris host.
When the Oracle Solaris Cluster system detects a critical failure on any other type of node, for example, a global-cluster non-voting node or zone-cluster node, the system reboots that node.
Oracle Solaris Cluster software monitors the nodes that belong to the cluster. Communication or node failures can change the number of nodes in a cluster. If the cluster does not maintain sufficient votes, Oracle Solaris Cluster software halts that set of nodes.
Oracle Solaris Cluster software maintains a number of critical cluster-specific daemons. Some daemons support the global-cluster voting node, while others support other types of nodes. A daemon is critical to the node that the daemon supports, which might differ from the node on which the daemon runs. For example, some daemons in the global zone support a non-global zone. For this reason, these daemons are critical to the health of the non-global zone rather than the global zone.