Skip to main content
Tungsten Clustering

Adding Connectors to an Existing Deployment

Adding more connectors to an existing installation allows for increased routing capacity. The new connectors will form part of the cluster and be fully aware and communicate with existing managers and datasources within the cluster.

To add more connectors to an existing deployment:

  1. On the new host, ensure the "Installation Prerequisites" have been followed.

  2. On all existing nodes, update the /etc/tungsten/tungsten.ini configuration file adding the new host to the list of connectors.

    Example tungsten.ini
    [alpha]
    ...
    connectors=host4
    Show argument definitions
    connectors=host4Hostnames for the dataservice connectors.
  3. Using the --no-connectors option updates the current deployment without restarting the existing connectors.

  4. During a period when it is safe to restart the connectors:

    shell> ./tools/tpm promote-connector
  5. Copy the /etc/tungsten/tungsten.ini from an existing node to the new connector being configured.

    Note

    If SSL is enabled, you should also copy the various SSL keys and certificated from /opt/continuent/share of an existing connector to the new connector.

  6. Install the Tungsten Cluster package or download the Tungsten Cluster tarball, and unpack it on the new Connector host:

    shell> cd /opt/continuent/software
    shell> tar zxf tungsten-clustering-8.0.4-132.tar.gz
  7. Change to the Tungsten Cluster directory:

    shell> cd tungsten-clustering-8.0.4-132
  8. Run tpm to validate the installation. Providing no errors are returned, you can then continue to install the software.

    shell > ./tools/tpm validate
    shell > ./tools/tpm install
  9. If your connectors are using Proxy, you will need to copy the user.map file from an existing connector to ensure authentication of clients succeeds.

  10. If you supplied start-and-report the software will be running, if this wasn't included, you can now start the software as follows:

    shell > connector start

The status of all the connectors can be monitored using cctrl:

[LOGICAL] /alpha > ls

COORDINATOR[host1:AUTOMATIC:ONLINE]

ROUTERS:
+----------------------------------------------------------------------------+
|connector@host1[8616](ONLINE, created=0, active=0) |
|connector@host2[12381](ONLINE, created=0, active=0) |
|connector@host3[19708](ONLINE, created=0, active=0) |
|connector@host4[5085](ONLINE, created=0, active=0) |
+----------------------------------------------------------------------------+