1. Overview of Resource Management
3. Resource Management API Reference
6. Data Service Development Library
8. Sample DSDL Resource Type Implementation
9. Solaris Cluster Agent Builder
12. Cluster Reconfiguration Notification Protocol
B. Sample Data Service Code Listings
C. DSDL Sample Resource Type Code Listings
E. Requirements for Non-Cluster Aware Applications
F. Document Type Definitions for the CRNP
This section describes the cluster properties that are defined by the Oracle Solaris Cluster software.
The property values are categorized as follows:
Required. The cluster administrator must specify a value when he or she creates a cluster with an administrative utility.
Optional. If the cluster administrator does not specify a value when he or she creates a cluster, the system supplies a default value.
Conditional.The RGM creates the property only if the property is declared in the RTR file. Otherwise, the property does not exist and is not available to cluster administrators. A conditional property that is declared in the RTR file is optional or required, depending on whether a default value is specified in the RTR file. For details, see the description of each conditional property.
Query-only. Cannot be set directly by an administrative tool.
The Tunable attribute, which is described in Resource Property Attributes, lists whether and when you can update resource properties, as follows:
Never
Any time
When the resource is added to a cluster
When the resource is disabled
Property names are listed first, followed by a description.
Specifies how the Resource Group Manager (RGM) distributes the resource group load across the available nodes. The concentrate_load property can be set only in a global cluster. In zone clusters, the concentrate_load property has the default value of FALSE. If the value is set to FALSE in a global cluster, the RGM attempts to spread resource group load evenly across all available nodes or zones in the resource groups' node lists. If the value is set to TRUE, the resource group load is concentrated on the fewest possible nodes or zones without exceeding any configured hard or soft load limits. The default value is FALSE.
Hard and soft load limits for each node are created and modified with the clnode create-loadlimit, clnode set-loadlimit, and clnode delete-loadlimit command.
Optional
FALSE
ANYTIME