NAME | DESCRIPTION | SEE ALSO
The list below describes the resource group properties that are defined by Sun Cluster.
Resource group property names, such as Auto_start_on_new_cluster and Desired_primaries, are not case sensitive. You can use any combination of uppercase and lowercase letters when you specify resource group property names.
This property controls whether the Resource Group Manager (RGM) starts the resource group automatically when a new cluster is forming. The default is True.
If set to True, the RGM attempts to start the resource group automatically to achieve Desired_primaries when all the nodes of the cluster are simultaneously rebooted.
If set to False, the resource group does not start automatically when the cluster is rebooted. The resource group remains offline until the first time that the resource group is manually switched online by using scswitch(1M) or the equivalent graphical user interface command. After that, the resource group resumes normal failover behavior.
True
Any time
The desired number of nodes that the group can run on simultaneously.
The default is 1. If the RG_mode property is Failover, the value of this property must be no greater than 1. If the RG_mode property is Scalable, a value greater than 1 is allowed.
1, see above
Any time
A Boolean value that indicates whether to recalculate the set of nodes where the group is online when the cluster membership changes. A recalculation can cause the RGM to bring the group offline on less preferred nodes and online on more preferred nodes.
False
Any time
Indicates whether cluster file systems are used by any resource in this resource group. Legal values that the administrator can specify are an asterisk (*) to indicate all global resources, and the empty string (“”) to indicate no global resources.
All global resources
Any time
A Boolean value that indicates, when True, that the RGM should enforce implicit strong dependencies of non-network-address resources on network-address resources within the group. This means that the RGM starts all network-address resources before all other resources and stops network address resources after all other resources within the group. Network-address resources include the logical host name and shared address resource types.
In a scalable resource group, this property has no effect because a scalable resource group does not contain any network-address resources.
True
Any time
The maximum number of nodes where the group might be online at once.
The default is 1. If the RG_mode property is Failover, the value of this property must be no greater than 1. If the RG_mode property is Scalable, a value greater than 1 is allowed.
1, see above
Any time
A comma-separated list of cluster nodes where the group can be brought online in order of preference. These nodes are known as the potential primaries or masters of the resource group.
The list of all cluster nodes in arbitrary order
Any time
A directory in the cluster file system that resources in the group can write essential administrative files in. Some resources might require this property. Make Pathprefix unique for each resource group.
The empty string
Any time
A non-negative integer value (in seconds) used by the RGM to determine where to bring the resource group online in the event of a reconfiguration or as the result of an scha_control giveover command or function being executed.
In the event of a reconfiguration, if the resource group fails more than once to come online within the past Pingpong_interval seconds on a particular node (because the resource's Start or Prenet_start method exited nonzero or timed out), that node is considered ineligible to host the resource group and the RGM looks for another master.
If a scha_control(1HA) command or scha_control(3HA) giveover is executed on a given node by a resource, thereby causing its resource group to fail over to another node, the first node (on which scha_control was invoked) cannot be the destination of another scha_control giveover by the same resource until Pingpong_interval seconds have elapsed.
3,600 (one hour)
Any time
The list of resources that are contained in the group. You do not set this property directly. Rather, the RGM updates this property when the administrator adds or removes resources from the resource group.
No default
Never
A comma-separated list of resource group affinities. Each affinity consists of a prefix followed by the name of a resource group. The affinity indicates that the RGM is to try to locate this resource group on a node that is the current master of the given resource group (positive affinity), or to locate this resource group on a node that is not a current master of the given resource group (negative affinity). An example is ++group1,-group2.
Prefixes include: ++, or strong positive affinity, +, or weak positive, -, or weak negative, --, or strong negative, and +++, or strong positive with failover delegation.
Strong affinities (RG_affinities settings ++, or strong positive, --, or strong negative, and +++, or strong positive with failover delegation) are strictly enforced. This resource group is never brought online, nor allowed to remain online on a node on which a resource group in the list is not online (strong positive affinity) or offline (strong negative affinity). That is, this resource group “follows” a group for which it has a strong positive affinity, and “moves away from” a group for which it has a strong negative affinity. If a strong affinity cannot be satisfied on a node (based on the current state of other resource groups), the group remains offline. If other resource groups' states change and the group's strong affinities can then be satisfied, the group comes back online. The graph of all strong RG_affinities (positive and negative) together with RG_dependencies is not allowed to contain cycles.
A strong positive affinity with failover delegation (+++) provides a “mutual” strong positive affinity with respect to scha_control giveovers. For example, if resource group RG1 declares a strong positive affinity with failover delegation for RG2, a resource from RG1 can perform a giveover and take RG2 along with it. The giveover request that originates from the resource in RG1 is “delegated” to RG2. RG2 executes the giveover, and drags RG1 along with it.
By contrast, if resource group RG1 declares only a strong positive affinity (++) for resource group RG2, and if both RG1 and RG2 are online on node1, if a resource in RG1 attempts to execute scha_control GIVEOVER (and assuming that RG2 is not currently online on any node other than node1), the giveover attempt fails. In other words, the resource group RG1, which declares a strong affinity without failover delegation, can only execute a giveover successfully if its strong affinity is already satisfied on another node.
The strong positive affinity with failover delegation is not fully symmetric. For example, RG2 comes online by itself while RG1 remains offline, but if RG2 is offline, RG1 cannot come online.
In the preceding example, if RG2 declares a strong positive affinity with failover delegation for another resource group RG3, the giveover request is further delegated to RG3. RG3 performs the giveover and drags both RG2 and RG1 with it.
A resource group is permitted to declare, at most, only one strong positive affinity with failover delegation. However, a given resource group can be the target of strong positive affinities with failover delegation that are declared by any number of other resource groups.
Weak affinities (RG_affinities settings + (or weak positive) and - (or weak negative)) are satisfied on a “best effort” basis and are not strictly enforced. When this resource group is brought online (for example, after a failover), the RGM attempts to choose a node that satisfies the greatest number of its weak affinities. Weak affinities take precedence over Nodelist preference ordering. The weak affinities of this group do not cause it to change nodes in response to the movement of other groups. Cycles are permitted in the graph of weak RG_affinities.
Use caution when listing more than one strong affinity in RG_affinities of a given resource group. If all declared strong affinities cannot be satisfied, the group remains offline.
The empty string
Any time
A comma-separated list of resource groups on which this group depends. This list indicates a preferred order for bringing other groups online or offline on the same node. It has no effect if the groups are brought online on different nodes.
The empty list
Any time
A brief description of the resource group.
The empty string
Any time
A Boolean value that indicates whether a global device on which a resource group depends is being switched over. If this property is set to True, the global device is being switched over. If this property is set to False, no global device is being switched over. A resource group depends on global devices as indicated by its Global_resources_used property.
You do not set the RG_is_frozen property directly. Rather, the RGM updates the RG_is_frozen property when the status of the global devices changes.
No default
Never
Indicates whether the resource group is a failover or a scalable group. If the value is set to Failover, the RGM sets the Maximum_primaries property of the group to 1 and restricts the resource group to being mastered by a single node.
If the value of this property is set to Scalable, the RGM allows the Maximum_primaries property to be set to a value that is greater than 1, meaning that the group can be mastered by multiple nodes simultaneously.
The RGM does not allow a resource whose Failover property is set to True to be added to a resource group whose RG_mode is Scalable.
If Maximum_primaries is set to 1 when a resource group is created, RG_mode is set to Failover by default. If Maximum_primaries is set to a value that is greater than 1 when a resource group is created, RG_mode is set to Scalable by default. Once a resource group is created, you cannot change RG_mode, even if Maximum_primaries changes.
At creation
The name of the resource group. This property is required and must be unique within the cluster.
No default
At creation
The Solaris project name (see projects(1)) that is associated with the resource group. Use this property to apply Solaris resource management features, such as CPU shares and resource pools, to cluster data services. When the RGM brings resource groups online, it launches the related processes under this project name for resources that do not have the Resource_project_name property set (see r_properties(5)). The specified project name must exist in the projects database, and the user root must be configured as a member of the named project (see projects(1) and System Administration Guide: Resource Management and Network Services).
This property is only supported starting in Solaris 9.
Changes to this property take affect the next time the resource is started.
The text “default”
Any time
Any valid Solaris project name
Set by the RGM to Unmanaged, Online, Offline, Pending_online, Pending_offline, Error_stop_failed, Online_faulted, or Pending_online_blocked to describe the state of the group on each cluster node. You cannot configure this property. A group can exist in an unmanaged state when that group is not under the control of the RGM. The following descriptions summarize each state.
States apply to individual nodes only, except the Unmanaged state, which applies across all nodes. For example, a resource group might be Offline on node A, but Pending_online on node B.
The initial state of a newly created resource group, or the state of a previously managed resource group. Either Init methods have not yet been run on resources in the group, or Fini methods have been run on resources in the group.
The group is not managed by the RGM.
The resource group has been started on the node. In other words, the starting methods (Prenet_start, Start, and Monitor_start, as applicable to each resource) have executed successfully on all enabled resources in the group.
The resource group has been stopped on the node. In other words, the stopping methods (Monitor_stop, Stop, and Postnet_stop, as applicable to each resource) have executed successfully on all enabled resources in the group. This state also applies before a resource group has started for the first time on the node.
The resource group is starting on the node. The starting methods (Prenet_start, Start, and Monitor_start, as applicable to each resource) are being executed on enabled resources in the group.
The resource group is stopping on the node. The stopping methods (Monitor_stop, Stop, and Postnet_stop, as applicable to each resource) are being executed on enabled resources in the group.
One or more resources within the resource group failed to stop successfully and are in Stop_failed state. Other resources in the group might remain online or offline. This resource group is not permitted to start on any node until the Error_stop_failed state is cleared.
You must use an administrative command, such as scswitch -c, to manually kill the Stop_failed resource and reset its state to Offline.
The resource group was Pending_online and has finished starting on this node. However, one or more resources ended up in Start_failed state or with Faulted status.
The resource group failed to start fully because one or more resources within that resource group have an unsatisfied strong resource dependency on a resource in a different resource group. Such resources remain Offline. When the resource dependencies are satisfied, the resource group automatically moves back to Pending_online state.
No default
Never
If the RG_System property is True for a resource group, particular operations are restricted for the resource group and for the resources that the resource group contains. This is intended to help prevent accidental modification or deletion of critical resource groups and resources. Only scrgadm(1M) and scswitch(1M) commands are affected by this property. Operations for scha_control(1HA) and scha_control(3HA) are not affected.
Before performing a restricted operation on a resource group (or a resource group's resources), you must first set the RG_System property of the resource group to False. Use care when you modify or delete a resource group that supports cluster services, or when you modify or delete the resources that such a resource group contains.
The following table shows the operations that are restricted for a resource group when RG_System is set to True.
Operation |
Example |
---|---|
Delete a resource group |
scrgadm -r -g RG1 |
Edit a resource group property (except for RG_System) |
scrgadm -c -t RG1 -y nodelist=... |
Add a resource to a resource group |
scrgadm -a -j R1 -g RG1 |
Delete a resource from a resource group |
scrgadm -r -j R1 -g RG1 |
Edit a property of a resource that belongs to a resource group |
scrgadm -c -j R1 |
Switch a resource group offline |
scswitch -F -g RG1 |
Switch a resource group onto specified primaries |
scswitch -z -g -G1 -h node1 |
Manage a resource group |
scswitch -o -g RG1 |
Unmanage a resource group |
scswitch -u -g RG1 |
Enable a resource |
scswitch -e -j R1 |
Enable a monitor for a resource |
scswitch -e -M -j R1 |
Disable a resource |
scswitch -n -j R1 |
Disable a monitor for a resource |
scswitch -n -M -j R1 |
If the RG_System property is True for a resource group, the only property of the resource group that you can edit is the RG_System property itself. In other words, editing the RG_System property is never restricted.
False
Any time
projects(1), scha_control(1HA), scrgadm(1M), scswitch(1M), scha_control(3HA), property_attributes(5), r_properties(5), rt_properties(5)
System Administration Guide: Resource Management and Network Services
NAME | DESCRIPTION | SEE ALSO