Tungsten Clustering

Upgrading using the INI Method

To perform an upgrade of an individual node, tpm can be used on the individual host.

warning

Before performing an upgrade, please ensure that you have checked the "Installation Prerequisites", as software and system requirements may have changed between versions and releases.

important

Application traffic to the nodes will be disconnected when the connector restarts. Use the --no-connectors tpm option when you upgrade to prevent the connectors from restarting until later when you want them to.

note

For more information on performing maintenance across a cluster, see "Performing Maintenance on an Entire Dataservice"

To upgrade a single host using the tpm command:

Download the release package.
Unpack the release package into the staging directory, typically /opt/continuent/software:
```
shell> cd /opt/continuent/software
shell> tar tungsten-clustering-8.0.4-132.tar.gz
```
Change to the extracted directory:
```
shell> cd tungsten-clustering-8.0.4-132
```
Place your cluster into MAINTENANCE mode:
```
cctrl> set policy maintenance
```
For composite clusters, either issue this per cluster, or issue at the composite level:
```
cctrl> use global
cctrl> set policy maintenance
```
Execute tpm update, specifying the installation directory. This will update only this host, and will therefore need repeating on all nodes in the cluster:
```
shell> ./tools/tpm update --replace-release
```
The following additional option is available, and would be recommended in production environments for hosts running connector services, or when updating standalone connector hosts:
- --no-connectors
  By default, an update process will restart all services, including the connector. Adding this option prevents the connectors from being restarted. If this option is used, the connectors must be manually updated to the new version during a quieter period. This can be achieved by running, on each host, the following command:
```
shell> tpm promote-connector
```
  This will result in a short period of downtime (couple of seconds) only on the host concerned, while the other connectors in your configuration keep running. During the upgrade, the Connector is restarted using the updated software and/or configuration.
When all nodes are complete, return your cluster into AUTOMATIC mode:
```
cctrl> set policy automatic
```
For composite clusters, either issue this per cluster, or issue at the composite level:
```
cctrl> use global
cctrl> set policy automatic
```
If your connectors are running on dedicated hosts, the same update steps will need repeating on all connector hosts, however the cluster does NOT need to be in MAINTENANCE mode when upgrading the connectors, but you should be aware that the update will restart the connector and existing connections will be terminated, therefore this should be carried out with care during a maintenance window and consider the additional --no-connectors option.