JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Overview
search filter icon
search icon

Document Information

Preface

1.  Introduction to Oracle Solaris Cluster

2.  Key Concepts for Oracle Solaris Cluster

Clusters, Nodes, and Hosts

Zone Cluster

Features and Benefits of a Zone Cluster

Cluster Interconnect

Cluster Membership

Cluster Configuration Repository

Quorum Devices

Fault Monitors

Data Services Monitoring

Disk-Path Monitoring

IP Multipath Monitoring

Quorum Device Monitoring

Data Integrity

Split Brain and Amnesia

Fencing

Failfast

Shared Devices, Local Devices, and Device Groups

Shared Devices

How Oracle Solaris Cluster Uses Shared Devices

Device ID

Local Devices

Device Groups

Data Services

Description of a Resource Type

Description of a Resource

Description of a Resource Group

Data Service Types

Description of a Failover Data Service

Description of a Scalable Data Service

Description of a Parallel Application

System Resource Usage

System Resource Monitoring

CPU Control

Visualization of System Resource Usage

3.  Oracle Solaris Cluster Architecture

Index

Data Services

A data service is the combination of software and configuration files that enables an application to run without modification in an Oracle Solaris Cluster configuration. When running in an Oracle Solaris Cluster configuration, an application runs as a resource under the control of the Resource Group Manager (RGM). A data service enables you to configure an application such as Sun Java System Web Server or Oracle database to run on a cluster instead of on a single server.

The software of a data service provides implementations of Oracle Solaris Cluster management methods that perform the following operations on the application:

The configuration files of a data service define the properties of the resource that represents the application to the RGM.

The RGM controls the disposition of the failover and scalable data services in the cluster. The RGM is responsible for starting and stopping the data services on selected nodes of the cluster in response to cluster membership changes. The RGM enables data service applications to utilize the cluster framework.

The RGM controls data services as resources. These implementations are either supplied by Oracle or created by a developer who uses a generic data service template, the Data Service Development Library API (DSDL API), or the Resource Management API (RMAPI). The cluster administrator creates and manages resources in containers that are called resource groups. RGM and administrator actions cause resources and resource groups to move between online and offline states.

Description of a Resource Type

A resource type is a collection of properties that describe an application to the cluster. This collection includes information about how the application is to be started, stopped, and monitored on nodes of the cluster. A resource type also includes application-specific properties that need to be defined in order to use the application in the cluster. Oracle Solaris Cluster data services has several predefined resource types. For example, Oracle Solaris Cluster HA for Oracle is the resource type SUNW.oracle-server and Oracle Solaris Cluster HA for Apache is the resource type SUNW.apache.

Description of a Resource

A resource is an instance of a resource type that is defined cluster wide. The resource type enables multiple instances of an application to be installed on the cluster. When you initialize a resource, the RGM assigns values to application-specific properties and the resource inherits any properties on the resource type level.

Data services utilize several types of resources. Applications such as Apache Web Server or Sun Java System Web Server utilize network addresses (logical hostnames and shared addresses) on which the applications depend. Application and network resources form a basic unit that is managed by the RGM.

Description of a Resource Group

Resources that are managed by the RGM are placed into resource groups so that they can be managed as a unit. A resource group is a set of related or interdependent resources. For example, a resource derived from a SUNW.LogicalHostname resource type might be placed in the same resource group as a resource derived from an Oracle database resource type. A resource group migrates as a unit if a failover or switchover is initiated on the resource group.

Data Service Types

Data services enable applications to become highly available and scalable services help prevent significant application interruption after any single failure within the cluster.

When you configure a data service, you must configure the data service as one of the following data service types:

Description of a Failover Data Service

Failover is the process by which the cluster automatically relocates an application from a failed primary node to a designated redundant secondary node. Failover applications have the following characteristics:

If the fault monitor detects an error, it either attempts to restart the instance on the same node, or to start the instance on another node (failover), depending on how the data service has been configured. Failover services use a failover resource group, which is a container for application instance resources and network resources (logical hostnames). Logical hostnames are IP addresses that can be configured up on one node, and later, automatically configured down on the original node and configured up on another node.

Clients might have a brief interruption in service and might need to reconnect after the failover has finished. However, clients are not aware of the change in the physical server that is providing the service.

Description of a Scalable Data Service

The scalable data service enables application instances to run on multiple nodes simultaneously. Scalable services use two resource groups. The scalable resource group contains the application resources and the failover resource group contains the network resources (shared addresses) on which the scalable service depends. The scalable resource group can be online on multiple nodes, so multiple instances of the service can be running simultaneously. The failover resource group that hosts the shared address is online on only one node at a time. All nodes that host a scalable service use the same shared address to host the service.

The cluster receives service requests through a single network interface (the global interface). These requests are distributed to the nodes, based on one of several predefined algorithms that are set by the load-balancing policy. The cluster can use the load-balancing policy to balance the service load between several nodes.

Description of a Parallel Application

Oracle Solaris Cluster systems provide an environment that shares parallel execution of applications across all the nodes of the cluster by using parallel databases. Oracle Solaris Cluster Support for Oracle Real Application Clusters is a set of packages that, when installed, enables Oracle Real Application Clusters to run on Oracle Solaris Cluster nodes. This data service also enables Oracle Solaris Cluster Support for Oracle Real Application Clusters to be managed by using Oracle Solaris Cluster commands.

A parallel application has been instrumented to run in a cluster environment so that the application can be mastered by two or more nodes simultaneously. In an Oracle Real Application Clusters environment, multiple Oracle instances cooperate to provide access to the same shared database. The Oracle clients can use any of the instances to access the database. Thus, if one or more instances have failed, clients can connect to a surviving instance and continue to access the database.