Resource Group Properties

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

• Required – The administrator must specify a value when creating a resource group with an administrative utility.

• Optional – If the administrator does not specify a value when creating a resource group, the system supplies a default value.

• Query-only – Cannot be set directly by an administrative tool.

Each description states whether the property can be updated (Yes) or not (No) after it is initially set.

Property names are shown first, followed by a description.

Auto_start_on_new_cluster (boolean)

This property disallows automatic startup of the Resource Group when a new cluster is forming.

If set to TRUE, the Resource Group Manager attempts to start the resource group automatically to achieve Desired_primaries when the cluster is rebooted. If set to FALSE, the Resource Group does not start automatically when the cluster reboots.

Category:

Optional

Default:

TRUE

Tunable:

Yes

Desired_primaries (integer)

The number of nodes where the group is desired to be online at once.

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:

Yes

Failback (boolean)

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.

Category:

Optional

Default:

FALSE

Tunable:

Yes

Global_resources_used (string_array)

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.

Category:

Optional

Default:

All global resources

Tunable:

Yes

Implicit_network_dependencies (boolean)

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. 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:

Yes

Maximum_primaries (integer)

The maximum number of nodes where the group might be online at once.

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:

Yes

Nodelist (string_array)

A 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.

Category:

Optional

Default:

The list of all cluster nodes

Tunable:

Yes

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:

Yes

Pingpong_interval (integer)

A nonnegative integer value (in seconds) that is used by the RGM to determine where to bring the resource group online. Conditions under which this property might be needed are as follows:

• If a reconfiguration occurs

• A scha_control -O GIVEOVER command or a scha_control() function with the SCHA_GIVEOVER argument is executed

If a reconfiguration occurs, if the resource group fails to come online more than once within the past Pingpong_interval seconds on a particular node, that node is considered ineligible to host the resource group and the RGM looks for another master. The resource group fails to come online because the resource's Start or Prenet_start method exited nonzero or timed out.

If a call to a resource's scha_control command or function causes the resource group to be brought offline on a particular node within the past Pingpong_interval seconds, that node is ineligible to host the resource group as the result of a subsequent call to scha_control() that originates from another node.

Category:

Optional

Default:

3600 (one hour)

Tunable:

Yes

Resource_list (string_array)

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

Category:

Query-only

Default:

No default

Tunable:

No

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 to locate a resource group on a node 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 “Administering Data Service Resources” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

Category:

Optional

Default:

The empty string

Tunable:

Yes

RG_dependencies (string_array)

Optional list of resource groups that indicate 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. In other words, suppose that 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. scswitch(1M) and scsetup(1M) 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:

Yes

RG_description (string)

A brief description of the resource group.

Category:

Optional

Default:

The empty string

Tunable:

Yes

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:

No

RG_mode (enum)

Indicates whether the resource group is a failover or 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 have a value 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:

No

RG_name (string)

The name of the resource group. This name must be unique within the cluster.

Category:

Required

Default:

No default

Tunable:

No

RG_project_name (string)

The Solaris project name 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. The specified project name must exist in the projects database and the user root must be configured as a member of the named project.

This property is supported in Solaris 9 and later versions of Solaris only.

---

Note –

Changes to this property take effect the next time 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, Pending_online_blocked, 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 invoking scswitch(1M), or by using the equivalent scsetup(1M) or SunPlex Manager commands.

Category:

Query-only

Default:

No default

Tunable:

No

RG_system (boolean)

If the RG_system property is TRUE for a resource group, then 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 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.

A resource group whose RG_system value is set to TRUE is called a system resource group. Editing the RG_system property itself is never restricted, regardless of the current value of RG_system. The rg_properties(5) man page describes these restrictions in more detail.

Category:

Optional

Default:

FALSE

Tunable:

Yes