Suspending a Persistence Cluster

You can suspend all the services in a persistence cluster, however, you cannot suspend a service individually.

Suspending a cluster is a prerequisite subtask to saving the state of its services (the subtask that follows).

In addition, the suspend command can be used with the disaster recovery feature for planned failback. Once the suspend command is issued at the site that is currently active, the persistence services at that site will stop accepting message and acknowledgement data from clients and/or routes. Instead, they will finish replicating all stored data to the current standby site.

If authentication and authorization are enabled, you must be in the ftl-admin authorization group to do this task.

Note: Services in a suspended cluster transition to a suspended state. Suspended services do not communicate with clients, nor with other services. Their only available operation is to save their state to a file. Disaster recovery persistence services can also be activated after the active persistence services were suspended.
Note: You cannot suspend the internal cluster ftl.default.cluster.
    Procedure
  1. Open the persistence clusters status table.
  2. Locate the cluster to suspend, and click its Suspend icon.
  3. Confirm.
  4. Wait until all the services in the cluster are suspended.

    To verify suspension, check for the pause icon in the Service Status column of the services list, or check the persistence service log messages.

What to do next

Saving the State of a Persistence Service