Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Services Developer's Guide Oracle Solaris Cluster 3.3 3/13 |
1. Overview of Resource Management
3. Resource Management API Reference
Defining the Resource Type Registration File
Resource Type Properties in the Sample RTR File
Resource Properties in the Sample RTR File
System-Defined Properties in the RTR File
Extension Properties in the RTR File
Providing Common Functionality to All Methods
Identifying the Command Interpreter and Exporting the Path
Declaring the PMF_TAG and SYSLOG_TAG Variables
Parsing the Function Arguments
Obtaining Property Information
Checking the Reliability of the Service
Comparing Restart With Failover
How the Monitor_start Method Works
What the Monitor_start Method Does
How the Monitor_stop Method Works
What the Monitor_stop Method Does
How the Monitor_check Method Works
Validate Method Parsing Function
Stopping the Monitor With Update
6. Data Service Development Library
8. Sample DSDL Resource Type Implementation
9. Oracle Solaris Cluster Agent Builder
12. Cluster Reconfiguration Notification Protocol
13. Security for Data Services
A. Sample Data Service Code Listings
B. DSDL Sample Resource Type Code Listings
C. Requirements for Non-Cluster Aware Applications
D. Document Type Definitions for the CRNP
The sample data service starts, stops, restarts, and switches the DNS application among the nodes of the cluster in response to cluster events, such as administrative action, application failure, or node failure.
Application restart is managed by the Process Monitor Facility (PMF). If the number of applications that die exceeds the failure count within the failure time window, the fault monitor fails over the resource group that contains the application resource to another node.
The sample data service provides fault monitoring in the form of a PROBE method that uses the nslookup command to ensure that the application is healthy. If the probe detects a hung DNS service, the probe tries to correct the situation by restarting the DNS application locally. If restarting the DNS application locally does not improve the situation and the probe repeatedly detects problems with the service, the probe attempts to fail over the service to another node in the cluster.
Specifically, the sample data service includes the following elements:
A resource type registration file that defines the static properties of the data service.
A Start callback method that is run by the RGM to start the in.named daemon when the resource group that contains the HA-DNS data service is brought online.
A Stop callback method that is run by the RGM to stop the in.named daemon when the resource group that contains HA-DNS goes offline.
A fault monitor to check the availability of the service by verifying that the DNS server is running. The fault monitor is implemented by a user-defined PROBE method, and is started and stopped by the Monitor_start and Monitor_stop callback methods.
A Validate callback method that is run by the RGM to validate that the configuration directory for the service is accessible.
An Update callback method that is run by the RGM to restart the fault monitor when the cluster administrator changes the value of a resource property.