Stopping the cluster

Use this procedure to stop the applications that serviced is managing, serviced itself, and cluster services.
  1. Log in to Active-Node as root, or as a user with superuser privileges.
  2. Stop the top-level service serviced is managing, if necessary.
    1. Show the status of running services.
      serviced service status
      The top-level service is the service listed immediately below the headings line.
      • If the status of the top-level service and all child services is stopped, proceed to the next step.
      • If the status of the top-level service and all child services is not stopped, perform the remaining substeps.
    2. Stop the top-level service.
      Replace Service with the name or identifier of the top-level service:
      serviced service stop Service
    3. Monitor the stop.
      serviced service status
      When the status of the top-level service and all child services is stopped, proceed to the next step.
  3. Disable serviced.
    pcs resource disable serviced
  4. Stop serviced on all delegate hosts.
    For more information, see Stopping a delegate host.
  5. Disable additional resources.
    1. Disable storage resources.
      pcs resource disable serviced-storage
    2. Disable the serviced group.
      pcs resource disable serviced-group
  6. Confirm that all resources are stopped, and identify the master node.
    1. Confirm that all resources are stopped.
      watch pcs status
  7. Disable replication.
    pcs cluster standby --all
  8. In a separate terminal session, log in to Passive-Node as root, or as a user with superuser privileges.
  9. On both nodes, confirm that replication is disabled.
    drbd-overview
    The output should match the following example:
    0:serviced-dfs/0  Unconfigured . .
    1:serviced-dfs/1  Unconfigured . .
    2:serviced-dfs/2  Unconfigured . .
  10. On both nodes, display the size of the serviced thin pool device.
    Typically, the serviced thin pool device is associated with /dev/drbd2. To verify the configuration in your environment, review /etc/drbd.d/serviced-dfs.res.
    lsblk -ap --output=NAME,SIZE,TYPE,FSTYPE,MOUNTPOINT
    None of devices listed in the output should include subordinate DRBD devices.