Stopping and quiescing resources

You can stop or quiesce resources when you want to perform maintenance activities.

Before you begin

To stop a Teracloud® Streams resource, you must have root authority.

To quiesce a resource, you must have write authority for the hosts domain object. For more information, see User authorization for Teracloud® Streams.

About this task

Before you stop or quiesce resources, consider whether jobs or domain and instance services are running on the resources:
  • If there are jobs with processing elements that cannot be relocated to other resources, you cannot stop or quiesce the resources.
  • If management services are running on the resources, you must have standby services on other resources in the domain; otherwise, you cannot stop or quiesce those resources. For more information, see Configuring high availability in a Teracloud® Streams enterprise domain.
Note: You can force the quiesce or stop operation to complete, but doing so can cause one or more jobs to become unhealthy or the domain or instance to stop unexpectedly.

Procedure

  • To quiesce a Teracloud® Streams resource, use the Streams Console or the streamtool quiesceresource command.
  • To stop a Teracloud® Streams resource, use the streamtool stopdomainhost command.
    Note: You can use this command only when the domain controller service is running as a system service. You must run this command on the host that you are stopping.

Results

When you stop a Teracloud® Streams resource, all of the Teracloud® Streams services on the specified resource stop. When you quiesce a Teracloud® Streams resource, however, the domain controller service does not stop.

If Teracloud® Streams resource was dynamically allocated to the instance, it tries to find another resource to satisfy the resource specifications.

What to do next

To resume a Teracloud® Streams resource, use the Streams Console or the streamtool resumeresource command.