4.4.2. Removing a Composite Datasource/Cluster from an Existing Deployment

There are really three different ways to remove an entire composite datasource (cluster) service from an existing composite cluster, (CAP, DAA or CAA):

Internal Operations Reference

Important

For Reference Only

Below are the internal operations taken during the script processing, presented for clarity.

Do NOT perform any step below by hand.

For CAP, tpm update and tpm delete-service both run the Manager Cleanup Steps on each node

For CAA, tpm update and tpm delete-service both run the Manager Cleanup Steps and the Replicator Cleanup Steps on each node

  • Manager Cleanup Steps

    • Manager Cleanup Steps performed on a node in a service not being deleted

      • Delete the dataservice from the Manager layer using cctrl

      • Remove the matching service line from cluster-home/conf/dataservices.properties

    • Manager Cleanup Steps performed on a node in service to be removed

  • Replicator Cleanup Steps

    • Replicator Cleanup Steps performed on a node in a service not being deleted

      • Offline all Tungsten Replicator services

      • Remove the two tungsten/tungsten-replicator/conf/static-*_from_{service}.properties* files

      • Restart the Tungsten Replicator process

      • Online all Tungsten Replicator services

      • Delete the service-specific thl and relay subdirs

    • Replicator Cleanup Steps performed on a node in service to be removed

      • Offline all Tungsten Replicator services

      • Remove the two tungsten/tungsten-replicator/conf/static-*_from_{service}.properties* files

4.4.2.1. Removing a Composite Datasource/Cluster from an Existing Deployment Using tpm update

To remove an entire composite datasource (cluster) from an existing deployment using the tpm update command, you must perform the following steps on every node in the composite cluster, including the ones to be removed.

  1. Edit the tungsten.ini file on every node in the composite cluster you are keeping

  2. Delete the entire stanza for the cluster service you wish to remove

  3. Delete the cluster name from the composite service definition

  4. Save and exit the tungsten.ini file

  5. Execute the ./tools/tpm update --replace-release command from the staging directory.

    For more information about running tpm update, please see Section 10.2.4, “Configuration Changes with an INI file”.

Once the procedure is complete on all nodes, the service will no longer be visible in cctrl.

4.4.2.2. Removing a Composite Datasource/Cluster from an Existing Deployment Using tpm delete-service

To remove an entire composite datasource (cluster) from an existing deployment using the tpm delete-service command, you must perform the following steps on every node in the composite cluster, including the ones to be removed.

  1. Execute the tpm delete-service {service_name_here} command

  2. During the execution of the tpm command on every node in the composite cluster that you are keeping, you will be prompted to edit the tungsten.ini file

    This step will not be called if the node is due to be de-commissioned (i.e. the service has been deleted).

  3. Delete the entire stanza for the cluster service you wish to remove

  4. Delete the cluster name from the composite service definition

  5. Save and exit the tungsten.ini file

  6. tpm will complete the service deletion based on your edits. Once this is done on all of the nodes, the service will be gone from cctrl.