Using resource groups : Stopping a resource group
 
Stopping a resource group
Stop a resource group from running jobs by performing one of the following actions:
*Disabling the resource group
*Setting the resource group’s maximum number of Factory processes to 0 for all nodes that belong to the resource group
*Removing active membership of nodes
Disabling an asynchronous resource group is the same as setting the maximum number of Factory processes to 0. If all resource groups are disabled, jobs sent to the disabled asynchronous resource groups go into a pending state until a resource group becomes available.
If you disable a synchronous resource group, it processes jobs that are currently being executed and those that are waiting. If you set the maximum number of Factory processes to 0 on any of the nodes, jobs wait to be executed until they time out.
Removing all active memberships from a resource group is the same as setting the maximum number of Factory processes to 0 on all nodes in a cluster.
If you remove a resource group from an Encyclopedia volume, you must assign a resource group with available Factory processes to the Encyclopedia volume. Otherwise, you cannot run a job. For example, if you change a resource group Encyclopedia volume assignment from volume1 to volume2, you must ensure that another resource group can handle the jobs volume users create in volume1. If you remove an Encyclopedia volume assigned to a resource group, iHub changes the Encyclopedia volume’s resource group assignment to All volumes and disables the resource group.