How to Control CPU Usage in a Global-Cluster Non-Voting Node With the Default Processor Set

Perform this procedure if you want to assign CPU shares for resource groups in a global-cluster non-voting node, but do not need to create a dedicated processor set.

If a resource group is assigned CPU shares, Sun Cluster software performs the following tasks when starting a resource of that resource group in a non-voting node:

• Creates a pool named SCSLM_resource_group_name, if this has not already been done.

• Associates the SCSLM_pool_zone_name pool to the default processor set.

• Dynamically binds the non-voting node to the SCSLM_poolzone_name pool.

• Augments the number of CPU shares assigned to the non-voting node (zone.cpu-shares) with the specified number of CPU shares, if this has not already been done.

• Creates a project named SCSLM_resourcegroup_name in the non-voting node, if this has not already been done. This project is specific to the resource group, and is assigned the specified number of CPU shares (project.cpu-shares).

• Starts the resource in the SCSLM_resourcegroup_name project.

For more information about configuring the CPU control facility, see the rg_properties(5) man page.

1. Set the default scheduler for the system to be fair share scheduler (FSS).

   # dispadmin -d FSS

   FSS becomes the default scheduler on next reboot. To make this configuration take effect immediately, use the priocntl command:

   # priocntl -s -C FSS

   Using the combination of the priocntl and dispadmin commands ensures that FSS becomes the default schedule immediately and remains so after reboot. For more information about setting a scheduling class, see the dispadmin(1M) and priocntl(1) man pages.

   ---

   Note –

   If the FSS is not the default scheduler, your CPU shares assignment will not take effect.

   ---

2. On each node to use CPU control, configure the number of shares for the global-cluster voting node and the minimum number of CPUs available in the default processor set.

   Setting these parameters helps protect processes running in the voting node from competing for CPUs with processes running in global-cluster non-voting nodes. If you do not assign a value to the globalzoneshares and defaultpsetmin properties, these properties take their default values.

   # clnode set [-p globalzoneshares=integer] \ [-p defaultpsetmin=integer] \ node

   -p globalzoneshares=integer

   Sets the number of shares assigned to the voting node. The default value is 1.

   -p defaultpsetmin=defaultpsetmininteger

   Sets the minimum number of CPUs available in the default processor set. The default value is 1.

   node

   Identifies nodes on which properties are to be set.

   In setting these properties, you are setting properties for the voting node.

3. Verify that you correctly set these properties:

   # clnode show node

   For the node you specify, the clnode command prints the properties set and the values that are set for these properties. If you do not set the CPU control properties with clnode, they take the default value.

4. Configure the CPU control facility.

   # clresourcegroup create -p RG_SLM_TYPE=automated \ [-p RG_SLM_CPU_SHARES=value] resource_group_name

   -p RG_SLM_TYPE=automated

   Enables you to control CPU usage and automates some steps to configure the Solaris OS for system resource management.

   -p RG_SLM_CPU_SHARES=value

   Specifies the number of CPU shares assigned to the resource group-specific project (project.cpu-shares) and determines the number of CPU shares assigned to the global-cluster non-voting node (zone.cpu_shares).

   resource_group_name

   Specifies the name of the resource group.

   This step creates a resource group. You could alternatively use the clresourcegroup set command to modify an existing resource group.

   You cannot set RG_SLM_TYPE to automated in a non-voting node if a pool other than the default pool is in the zone configuration or if the zone is dynamically bound to a pool other than the default pool. See the zonecfg(1M) and poolbind(1M) man pages for information about zone configuration and pool binding respectively. View your zone configuration as follows:

   # zonecfg -z zone_name info pool

   ---

   Note –

   A resource such as an HAStoragePlus or a LogicalHostname resource was configured to start in a non-voting node but with the GLOBAL_ZONE property set to TRUE is started in the voting node. Even if you set the RG_SLM_TYPE property to automated, this resource does not benefit from the CPU shares configuration and is treated as in a resource group with RG_SLM_TYPE set to manual.

   ---

   In this procedure, you do not set the RG_SLM_PSET_TYPE property. Sun Cluster uses the default processor set.

5. Activate the configuration change.

   # clresourcegroup online -M resource_group_name

   resource_group_name

   Specifies the name of the resource group.

   If you set RG_SLM_PSET_TYPE to default, Sun Cluster creates a pool, SCSLM_pool_zone_name, but does not create a processor set. In this case, SCSLM_pool_zone_name is associated with the default processor set.

   If online resource groups are no longer configured for CPU control in a non-voting node, the CPU share value for the non-voting node takes the value of zone.cpu-shares in the zone configuration. This parameter has a value of 1 by default. For more information about zone configuration, see the zonecfg(1M) man page.

   ---

   Note –

   Do not remove or modify the SCSLM_resource_group_name project. You can add more resource control manually to the project, for example by configuring the project.max-lwps property. For more information, see the projmod(1M) man page.

   ---