 |
|
|
NAME
| | rg_properties- - resource group properties |
| |
The list below describes the resource group properties that are defined
by Sun Cluster. RG_name is the only required resource group
property.
Resource Group Properties and Descriptions
| |
-
Auto_start_on_new_cluster (Boolean)
- This property controls whether the Resource Group Manager
starts the resource group automatically when a new cluster is forming. The
default is TRUE.
If set to TRUE, the Resource Group Manager 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 will remain
offline until the first time that it is manually switched online using scswitch(1M) or the equivalent GUI command.
After that, it will resume normal failover behavior.
- Default
-
TRUE
- Tunable
- Any time
-
Desired_primaries (integer)
- 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.
- Default
- 1, see above
- Tunable
- Any time
-
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.
- Default
- FALSE
- Tunable
- Any time
-
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.
- Default
- All global resources
- Tunable
- Any time
-
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. 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.
- Default
-
TRUE
- Tunable
- Any time
-
Maximum_primaries (integer)
- 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.
- Default
- 1, see above
- Tunable
- Any time
-
Nodelist (string array)
- 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.
- Default
- The list of all cluster
nodes in arbitrary order
- Tunable
- Any time
-
Pathprefix (string)
- 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.
- Default
- The empty string
- Tunable
- Any time
-
Pingpong_interval (integer)
- 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 to come
online more than once within the past Pingpong_interval
seconds on a particular node (because the resource's START
or PRENET_START method exited non-zero or timed out), that
node is considered ineligible to host the resource group and the RGM looks
for another master.
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 originating from another node.
- Default
- 3,600 (one hour)
- Tunable
- Any time
-
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 when the administrator adds or removes resources from the resource
group.
- Default
- The empty list
- Tunable
- Never
-
RG_dependencies (string array)
- A comma-separated list of resource groups that this group
depends on. 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.
- Default
- The empty list
- Tunable
- Any time
-
RG_description (string)
- A brief description of the resource group.
- Default
- The empty list
- Tunable
- Any time
-
RG_is_frozen (Boolean)
- A Boolean value that indicates whether a global device on which a resource
group depends is being switched over. If set to TRUE, the
global device is being switched over. If 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.
The administrator does 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.
- Default
-
FALSE
- Tunable
- Never
-
RG_mode (enum)
- 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.Note – 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.
- Default
- 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.
- Tunable
- At creation
-
RG_name (string)
- The name of the resource group. This property is required and must be unique
within the cluster.
- Default
- No Default
- Tunable
- At creation
-
RG_project_name (string)
- The Solaris project name (see projects(1)) 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.Note – Changes to this property take effect after the resource has been
restarted.
- Default
- Name of the system default
project
- Tunable
- Any time
- Valid value
- Any valid Solaris project
name
-
RG_state on each cluster node (enum)
- Set by the RGM to Online, Offline, Pending_online, Pending_offline, or Error_stop_failed to describe the state
of the group on each cluster node. A group can also exist in an unmanaged
state when it is not under the control of the RGM.
This property is not user configurable.
- Default
- Offline
- Tunable
- Never
-
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 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 which 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 RG1 -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.
- Default
-
FALSE
- Tunable
- Any time
|
|
| Sun Cluster 3.1 | Go To Top | Last Changed 4 Nov 2003 |
Company Info
|
Contact
|
Copyright 2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
|
