To add active witnesses to an existing deployment, use tpm to update the configuration, adding the list of active witnesses and the list of all members within the updated dataservice configuration.
Active Witness hosts must have been prepared using the notes provided in Appendix B, Prerequisites. Active witnesses must be ble to resolve the hostnames of the other managers and hosts in the dataservice. Installation will fail if prerequisities and host availability and stability cannot be confirmed.
Update the /etc/tungsten/tungsten.ini> configuration file
adding the new host to the list of members,
adding the host against the witness option
and enabling the enable-active-witnesses option.
shell> vi /etc/tungsten/tungsten.ini[alpha]
...
members=host1,host2,host3,host4
witnesses=host4
enable-active-witnesses=true
Run the tpm command to update the software with the INI-based configuration:
shell>tpm query stagingtungsten@db1:/opt/continuent/software/tungsten-clustering-8.0.0-10 shell>echo The staging DIRECTORY is `tpm query staging| cut -d: -f2`The staging DIRECTORY is /opt/continuent/software/tungsten-clustering-8.0.0-10 shell>cd {STAGING_DIRECTORY}shell>./tools/tpm update --no-connectors
For information about making updates when using an INI file, please see Section 10.2.4, “Configuration Changes with an INI file”.
Using the --no-connectors option
updates the current deployment without restarting the existing
connectors.
Once installation has completed successfully, and the manager service has started on each configured active witness, the status can be determined using ls within cctrl:
[LOGICAL] /alpha > ls
COORDINATOR[host1:AUTOMATIC:ONLINE]
ROUTERS:
+----------------------------------------------------------------------------+
|connector@host1[20446](ONLINE, created=0, active=0) |
|connector@host2[21698](ONLINE, created=0, active=0) |
|connector@host3[30354](ONLINE, created=0, active=0) |
+----------------------------------------------------------------------------+
DATASOURCES:
+----------------------------------------------------------------------------+
|host1(slave:ONLINE, progress=8946, latency=0.000) |
|STATUS [OK] [2018/12/05 04:27:47 PM GMT] |
+----------------------------------------------------------------------------+
| MANAGER(state=ONLINE) |
| REPLICATOR(role=slave, master=host3, state=ONLINE) |
| DATASERVER(state=ONLINE) |
| CONNECTIONS(created=0, active=0) |
+----------------------------------------------------------------------------+
+----------------------------------------------------------------------------+
|host2(slave:ONLINE, progress=8946, latency=0.334) |
|STATUS [OK] [2018/12/05 04:06:59 PM GMT] |
+----------------------------------------------------------------------------+
| MANAGER(state=ONLINE) |
| REPLICATOR(role=slave, master=host3, state=ONLINE) |
| DATASERVER(state=ONLINE) |
| CONNECTIONS(created=0, active=0) |
+----------------------------------------------------------------------------+
+----------------------------------------------------------------------------+
|host3(master:ONLINE, progress=8946, THL latency=0.331) |
|STATUS [OK] [2018/11/20 05:39:14 PM GMT] |
+----------------------------------------------------------------------------+
| MANAGER(state=ONLINE) |
| REPLICATOR(role=master, state=ONLINE) |
| DATASERVER(state=ONLINE) |
| CONNECTIONS(created=0, active=0) |
+----------------------------------------------------------------------------+
WITNESSES:
+----------------------------------------------------------------------------+
|host4(witness:ONLINE) |
+----------------------------------------------------------------------------+
| MANAGER(state=ONLINE) |
+----------------------------------------------------------------------------+Validation of the cluster with the new witnesses can be verified by using the cluster validate command within cctrl.