test

Sun Cluster Data Services Planning and Administration Guide for Solaris OS

Resource Group Properties

The following information describes the resource group properties that are defined by the Sun Cluster software. The property values are categorized as follows:

Property names are shown first, followed by a description.

Auto_start_on_new_cluster (boolean)

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 the scswitch command or the equivalent GUI instruction. After that, the resource group resumes normal failover behavior.

Category:

Optional

Default:

TRUE

Tunable:

ANYTIME

Desired_primaries (integer)

The preferred 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.

Category:

Optional

Default:

1

Tunable:

ANYTIME

Failback (boolean)

A Boolean value that indicates whether to recalculate the set of nodes on which 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.

Category:

Optional

Default:

FALSE

Tunable:

ANYTIME

Global_resources_used (string_array)

Indicates whether cluster file systems are used by any resource in this resource group. Legal values that the cluster administrator can specify are an asterisk (*) to indicate all global resources, and the empty string (“”) to indicate no global resources.

Category:

Optional

Default:

All global resources

Tunable:

ANYTIME

Implicit_network_dependencies (boolean)

A Boolean value that indicates, when TRUE, that the RGM should enforce implicit strong dependencies of nonnetwork 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.

Category:

Optional

Default:

TRUE

Tunable:

ANYTIME

Maximum_primaries (integer)

The maximum number of nodes on which the group might be online at the same time.

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.

Category:

Optional

Default:

1

Tunable:

ANYTIME

Nodelist (string_array)

A list of cluster nodes on which the group can be brought online in order of preference. These nodes are known as the potential primaries or masters of the resource group.

Category:

Optional

Default:

The list of all cluster nodes in arbitrary order

Tunable:

ANYTIME

Pathprefix (string)

A directory in the cluster file system in which resources in the group can write essential administrative files. Some resources might require this property. Make Pathprefix unique for each resource group.

Category:

Optional

Default:

The empty string

Tunable:

ANYTIME

Pingpong_interval (integer)

A nonnegative integer value (in seconds) that is used by the RGM to determine where to bring the resource group online in these instances:

  • In the event of a reconfiguration

  • As the result of the execution of a scha_control GIVEOVER command or function

In the event of a reconfiguration, the resource group might fail more than once to come online within the past Pingpong_interval seconds on a particular node. This failure occurs because the resource's Start or Prenet_start method exited with a nonzero status or timed out. As a result, that node is considered ineligible to host the resource group, and the RGM looks for another master.

If a scha_control command or scha_control GIVEOVER command 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 run) cannot be the destination of another scha_control GIVEOVER by the same resource until Pingpong_interval seconds have elapsed.

Category:

Optional

Default:

3600 (one hour)

Tunable:

ANYTIME

Resource_list (string_array)

The list of resources that are contained in the group. The cluster administrator does not set this property directly. Rather, the RGM updates this property as the cluster administrator adds or removes resources from the resource group.

Category:

Query-only

Default:

No default

Tunable:

NONE

RG_affinities (string)

The RGM is to try to locate a resource group on a node that is a current master of another given resource group (positive affinity) or that is not a current master of a given resource group (negative affinity).

You can set RG_affinities to the following strings:

  • ++, or strong positive affinity

  • +, or weak positive affinity

  • -, or weak negative affinity

  • --, or strong negative affinity

  • +++, or strong positive affinity with failover delegation

For example, RG_affinities=+RG2,--RG3 indicates that this resource group has a weak positive affinity for RG2 and a strong negative affinity for RG3.

Using RG_affinities is described in Chapter 2, Administering Data Service Resources.

Category:

Optional

Default:

The empty string

Tunable:

ANYTIME

RG_dependencies (string_array)

Optional list of resource groups that indicates a preferred ordering for bringing other groups online or offline on the same node. The graph of all strong RG_affinities (positive and negative) together with RG_dependencies is not allowed to contain cycles.

For example, suppose that resource group RG2 is listed in the RG_dependencies list of resource group RG1, that is, RG1 has a resource group dependency on RG2. The following list summarizes the effects of this resource group dependency:

  • When a node joins the cluster, Boot methods on that node are not run on resources in RG1 until all Boot methods on that node have completed on resources in RG2.

  • If RG1 and RG2 are both in the PENDING_ONLINE state on the same node at the same time, the starting methods (Prenet_start or Start) are not run on any resources in RG1 until all the resources in RG2 have completed their starting methods.

  • If RG1 and RG2 are both in the PENDING_OFFLINE state on the same node at the same time, the stopping methods (Stop or Postnet_stop) are not run on any resources in RG2 until all the resources in RG1 have completed their stopping methods.

  • An attempt to switch the primaries of RG1 or RG2 fails if switching the primaries would leave RG1 online on any node and RG2 offline on all nodes. The scswitch(1M) and scsetup(1M) man pages contain more information.

  • Setting the Desired_primaries property to a value that is greater than zero on RG1 is not permitted if Desired_primaries is set to zero on RG2.

  • Setting the Auto_start_on_new_cluster property to TRUE on RG1 is not permitted if Auto_start_on_new_cluster is set to FALSE on RG2.

Category:

Optional

Default:

The empty list

Tunable:

ANYTIME

RG_description (string)

A brief description of the resource group.

Category:

Optional

Default:

The empty string

Tunable:

ANYTIME

RG_is_frozen (boolean)

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. The RGM updates the RG_is_frozen property when the status of the global devices changes.

Category:

Optional

Default:

No default

Tunable:

NONE

RG_mode (enum)

Indicates whether the resource group is a failover or a scalable group. If the value is 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 Scalable, the RGM allows the Maximum_primaries property to be set to a value that is greater than 1. As a result, the group can be mastered by multiple nodes simultaneously. The RGM does not allow a resource whose Failover property is TRUE to be added to a resource group whose RG_mode is Scalable.

If Maximum_primaries is 1, the default is Failover. If Maximum_primaries is greater than 1, the default is Scalable.

Category:

Optional

Default:

Depends on the value of Maximum_primaries

Tunable:

NONE

RG_name (string)

The name of the resource group. This property is required and must be unique within the cluster.

Category:

Required

Default:

No default

Tunable:

NONE

RG_project_name (string)

The Solaris project name (see the projects(1) man page) 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 starts the related processes under this project name for resources that do not have the Resource_project_name property set (see the r_properties(5) man page). The specified project name must exist in the projects database (see the projects(1) man page and System Administration Guide: Solaris Containers-Resource Management and Solaris Zones).

This property is only supported starting in Solaris 9.

Note –

Changes to this property take affect the next time that the resource is started.

Category:

Optional

Default:

The text string “default”

Tunable:

ANYTIME

RG_state on each cluster node (enum)

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. However, you can indirectly set this property by running the scswitch command or by using the equivalent scsetup or SunPlex Manager commands. 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.

Note –

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.

UNMANAGED

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.

ONLINE

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.

OFFLINE

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.

PENDING_ONLINE

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.

PENDING_OFFLINE

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.

ERROR_STOP_FAILED

One or more resources within the resource group failed to stop successfully and are in the 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.

ONLINE_FAULTED

The resource group was PENDING_ONLINE and has finished starting on this node. However, one or more resources ended up in the Start_failed state or with Faulted status.

PENDING_ONLINE_BLOCKED

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 the PENDING_ONLINE state.

Category:

Query-only

Default:

No default

Tunable:

NONE

RG_system (boolean)

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 restriction is intended to help prevent accidental modification or deletion of critical resource groups and resources. Only the scrgadm and scswitch 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.

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

Manage a resource group 

scswitch -o -g RG1

Unmanage a resource group 

scswitch -u -g RG1

Enable a resource 

scswitch -e -j R1

Enable monitoring for a resource 

scswitch -e -M -j R1

Disable a resource 

scswitch -n -j R1

Disable monitoring 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.

Category:

Optional

Default:

FALSE

Tunable:

ANYTIME