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
When split brain occurs, not all nodes can communicate, so individual nodes or subsets of nodes might try to form individual or subset clusters. Each subset or partition might “believe” it has sole access and ownership to the multihost disks. Attempts by multiple nodes to write to the disks can result in data corruption.
If a node loses connectivity with other nodes, the node attempts to form a cluster with the nodes with which communication is possible. If that set of nodes does not form a quorum, Oracle Solaris Cluster software halts the node and “fences” the node from the disks. Thus, Oracle Solaris Cluster software prevents the node from accessing the disks. Only current member nodes have access to the disks, ensuring data integrity.
You can turn off fencing for selected disks or for all disks.
Caution - If you turn off fencing under the wrong circumstances, your data can be vulnerable to corruption during application failover. Examine this data corruption possibility carefully when you are considering turning off fencing. If your shared storage device does not support the SCSI protocol, such as a Serial Advanced Technology Attachment (SATA) disk, or if you want to allow access to the cluster's storage from hosts outside the cluster, turn off fencing. |