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:
On the new host, ensure the Appendix B, Prerequisites have been followed.
Update the configuration using tpm, adding the new
host to the list of connectors
If using the staging method of deployment, you can use
+=
, which appends the host to
the existing deployment as shown in the example below. Click the link to switch
between staging and ini type deployment examples.
shell>tpm query staging
tungsten@db1:/opt/continuent/software/tungsten-clustering-7.0.3-141 shell>echo The staging USER is `tpm query staging| cut -d: -f1 | cut -d@ -f1`
The staging USER is tungsten shell>echo The staging HOST is `tpm query staging| cut -d: -f1 | cut -d@ -f2`
The staging HOST is db1 shell>echo The staging DIRECTORY is `tpm query staging| cut -d: -f2`
The staging DIRECTORY is /opt/continuent/software/tungsten-clustering-7.0.3-141 shell>ssh {STAGING_USER}@{STAGING_HOST}
shell>cd {STAGING_DIRECTORY}
shell> ./tools/tpm configure alpha \
--connectors+=host4 \
Run the tpm command to update the software with the Staging-based configuration:
shell> ./tools/tpm update --no-connectors
For information about making updates when using a Staging-method deployment, please see Section 10.3.7, “Configuration Changes from a Staging Directory”.
shell> vi /etc/tungsten/tungsten.ini
[alpha]
...
connectors=host4
Run the tpm command to update the software with the INI-based configuration:
shell>tpm query staging
tungsten@db1:/opt/continuent/software/tungsten-clustering-7.0.3-141 shell>echo The staging DIRECTORY is `tpm query staging| cut -d: -f2`
The staging DIRECTORY is /opt/continuent/software/tungsten-clustering-7.0.3-141 shell>cd {STAGING_DIRECTORY}
shell>./tools/tpm update --no-connectors
For information about making updates when using an INI file, please see Section 10.4.4, “Configuration Changes with an INI file”.
Using the --no-connectors
option
updates the current deployment without restarting the existing
connectors.
During a period when it is safe to restart the connectors:
shell> ./tools/tpm promote-connector
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) |
+----------------------------------------------------------------------------+