Sun Cluster 3.2 Release Notes for Solaris OS

Data Services Developer's Guide

This section discusses errors and omissions in the Sun Cluster Data Services Developer’s Guide for Solaris OS.

Support of Certain Scalable Services on Non-Global Zones

In Resource Type Properties in Sun Cluster Data Services Developer’s Guide for Solaris OS, the description of the Failover resource property is missing a statement concerning support of scalable services on non-global zones. This support applies to resources for which the Failover property of the resource type is set to FALSE and the Scalable property of the resource is set to TRUE. This combination of property settings indicates a scalable service that uses a SharedAddress resource to do network load balancing. In the Sun Cluster 3.2 release, you can configure a scalable service of this type in a resource group that runs in a non-global zone. But you cannot configure a scalable service to run in multiple non-global zones on the same node.

Method Timeout Behavior is Changed

A description of the change in the behavior of method timeouts in the Sun Cluster 3.2 release is missing. If an RGM method callback times out, the process is now killed by using the SIGABRT signal instead of the SIGTERM signal. This causes all members of the process group to generate a core file.


Note –

Avoid writing a data-service method that creates a new process group. If your data service method does need to create a new process group, also write a signal handler for the SIGTERM and SIGABRT signals. Write the signal handlers to forward the SIGTERM or SIGABRT signal to the child process group before the signal handler terminates the parent process. This increases the likelihood that all processes that are spawned by the method are properly terminated.


CRNP Runs Only in the Global Zone

Chapter 12, Cluster Reconfiguration Notification Protocol, in Sun Cluster Data Services Developer’s Guide for Solaris OS is missing the statement that, on the Solaris 10 OS, the Cluster Reconfiguration Notification Protocol (CRNP) runs only in the global zone.

Required Solaris Software Group Statement is Unclear

In Setting Up the Development Environment for Writing a Data Service in Sun Cluster Data Services Developer’s Guide for Solaris OS, there is a Note that the Solaris software group Developer or Entire Distribution is required. This statement applies to the development machine. But because it is positioned after a statement about testing the data service on a cluster, it might be misread as a requirement for the cluster that the data service is being run on.