| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Cluster Overview |
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
A cluster is a collection of one or more nodes that belong exclusively to that collection. A global cluster and a zone cluster are types of clusters. A node is a Solaris zone that is associated with a cluster. In this environment, a Solaris host, or simply host, is one of the following hardware or software configurations that runs the Oracle Solaris OS and its own processes:
A “bare metal” physical machine that is not configured with a virtual machine or as a hardware domain
A Sun Logical Domains (LDoms) guest domain
A Sun Logical Domains (LDoms) I/O domain
A hardware domain
A voting node is a zone that contributes votes to the total number of quorum votes, that is, membership votes in a cluster. This total determines whether the cluster has sufficient votes to continue operating. A non-voting node is a zone that does not contribute to the total number of quorum votes, that is, membership votes in a cluster.
In a clustered environment, the nodes are connected by an interconnect and work together as a single entity to provide increased availability and performance.
A global cluster is a type of cluster that is composed only of one or more global-cluster voting nodes and optionally, zero or more global-cluster non-voting nodes.
Note - A global cluster can optionally also include lx (Linux), or native brand, non-global zones that are not nodes, but high availability containers (as resources).
A global-cluster voting node is a native brand, global zone in a global cluster that contributes votes to the total number of quorum votes, that is, membership votes in the cluster. This total determines whether the cluster has sufficient votes to continue operating. A global-cluster non-voting node is a native brand, non-global zone in a global cluster that does not contribute votes to the total number of quorum votes, that is, membership votes in the cluster.
A zone cluster is a type of cluster that is composed only of one or more cluster brand, voting nodes. A zone cluster depends on, and therefore requires, a global cluster. A global cluster does not contain a zone cluster. You cannot configure a zone cluster without a global cluster. A zone cluster has, at most, one zone cluster node on a machine.
Note - A zone-cluster node continues to operate only as long as the global-cluster voting node on the same machine continues to operate. If a global-cluster voting node on a machine fails, all zone-cluster nodes on that machine fail as well.
The Oracle Solaris Cluster software enables you to have one to sixteen Oracle Solaris hosts in a cluster, depending on the hardware configuration. Contact your Oracle representative for information about the number of Oracle Solaris hosts that are supported on your particular hardware configuration.
Oracle Solaris hosts in a cluster are generally attached to one or more disks. Oracle Solaris hosts that are not attached to disks use the cluster file system to access the multihost disks. Oracle Solaris hosts in parallel database configurations share concurrent access to some or all disks.
Every node in the cluster is aware when another node joins or leaves the cluster. Also, every node in the cluster is aware of the resources that are running locally as well as the resources that are running on the other cluster nodes.
Oracle Solaris hosts in the same cluster should have similar processing, memory, and I/O capability to enable failover to occur without significant degradation in performance. Because of the possibility of failover, each host should have sufficient capacity to meet service level agreements if a node fails.
|