Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Data Services Planning and Administration Guide Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

## Quiescing Resource Groups

To stop a resource group from continuously switching from one node to another when a `START` or `STOP` method fails, bring it to a quiescent state. To bring a resource group to a quiescent state, you issue the `clresourcegroup quiesce` command.

When you quiesce a resource group, resource methods that are executing are allowed to run until they are completed. If a serious problem occurs, you might need to quiesce a resource group immediately. To do so, you specify the `-k` command option, which kills the following methods:

- `Prenet_start`

- `Start`

- `Monitor_start`

- `Monitor_stop`

- `Stop`

- `Postnet_stop`

Note - The `Init`, `Fini` `Boot`, and `Update` methods are not killed when you specify this command option.

However, if you immediately quiesce a resource group by killing methods, you might leave one of its resources in an error state such as `Start_failed` or `Stop_failed`. You must clear these error states yourself.

## How to Quiesce a Resource Group

1. Assume the `root` role that provides `solaris.cluster.modify` RBAC authorization.
2. Quiesce the resource group.

       # clresourcegroup quiesce resource-group

## How to Quiesce a Resource Group Immediately

1. Assume the `root` role that provides `solaris.cluster.modify` RBAC authorization.
2. Immediately quiesce the resource group.

       # clresourcegroup quiesce -k resource-group

   The `Prenet_start`, `Start`, `Monitor_start`, `Monitor_stop`, `Stop`, and `Postnet_stop` methods that are associated with the resource group are killed immediately. The resource group is brought to a quiescent state.

   The `clresourcegroup quiesce -k` command blocks until the specified resource group has reached a quiescent state.

Copyright © 2000, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |