31.3. Disabling, enabling, and banning cluster resources

You can manually stop a running resource and prevent the cluster from starting it again with the following command. Depending on the rest of the configuration, such as constraints, options, and failures, the resource may remain started. If you specify the --wait option, pcs waits up to 'n' seconds for the resource to stop and then returns 0 if the resource is stopped or 1 if the resource has not stopped. If you do not specify n, it defaults to 60 minutes.

Simulating disabling a resource

Ensuring that disabling a resource would not have an effect on other resources can be impossible to do by hand when complex resource relations are set up. To determine what effect disabling a resource will have on other resources, use the pcs resource disable --simulate command to show the effects of disabling a resource while not changing the cluster configuration.

Safely disabling resources

You can specify that a resource be disabled only if disabling the resource would not have an effect on other resources.

Determining the resource IDs of affected resources

The error report that the pcs resource disable --safe command generates if the safe disable operation fails contains the affected resource IDs. If you need to know only the resource IDs of resources that would be affected by disabling a resource, use the --brief option for the pcs resource disable --safe command, which does not provide the full simulation result and prints errors only.

The following command allows the cluster to start a resource. Depending on the rest of the configuration, the resource may remain stopped. If you specify the --wait option, pcs will wait up to 'n' seconds for the resource to start and then return 0 if the resource is started or 1 if the resource has not started. If 'n' is not specified it defaults to 60 minutes.

You can prevent a resource from running on a specified node, or on the current node if no node is specified.

Use the debug-start parameter of the pcs resource command to force a specified resource to start on the current node, ignoring the cluster recommendations and printing the output from starting the resource. This is mainly used for debugging resources; starting resources on a cluster is (almost) always done by Pacemaker and not directly with a pcs command. If your resource is not starting, it is usually due to either a misconfiguration of the resource (which you debug in the system log), constraints that prevent the resource from starting, or the resource being disabled. You can use this command to test resource configuration, but it should not normally be used to start resources in a cluster.