2.6. Removing Datasources from a Deployment

Removing components from a dataservice is quite straightforward, usually involves both modifying the running service and changing the configuration. Changing the configuration is necessary to ensure that the host is not re-configured and installed when the installation is next updated.

2.6.1. Removing a Datasource from an Existing Deployment

To remove a datasource from an existing deployment there are two primary stages, removing it from the active service, and then removing it from the active configuration.

For example, to remove host6 from a service:

  1. Login to host6.

  2. Stop the replicator:

    shell> replicator stop
  3. Now you must remove the node from the configuration, although the exact method depends on whether you have multiple services in a single installation, if if the host was just running a single service:

    For a single service installation:

    • Remove the INI configuration file

      shell> rm /etc/tungsten/tungsten.ini
    • Next, uninstall the software:

      shell> cd /opt/continuent/software/tungsten-replicator-8.0.0-10.tar.gz
      shell> tools/tpm uninstall --i-am-sure
    • Optionally, remove the installed software directory:

      shell> rm -rf /opt/continuent
  4. For a Multiple-service installation:

    • Edit your /etc/tungsten/tungsten.ini and remove the service block that you wish to remove.

    • Issue an update from the software staging directory

      shell> cd /opt/continuent/software/tungsten-replicator-8.0.0-10.tar.gz
      shell> tools/tpm update --replace-release
    • Restart the replicator so that other services can resume.

      shell> replicator start