Tungsten Clustering

Upgrading using the Staging Method

important

As of v8, staging methods of installation and upgrade is deprecated and will be removed in a future release.

It is advisable to use the INI deployment method for existing and future deployments

To convert from staging to INI, see "Converting from Staging to INI"

note

For INI file upgrades, see "Upgrading using the INI Method"

warning

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

To perform an upgrade of an entire cluster from a staging directory installation, where you have ssh access to the other hosts in the cluster:

On your staging server, download the release package.

Unpack the release package:

shell> tar zxf tungsten-clustering-8.0.4-132.tar.gz

Change to the extracted directory:
```
shell> cd tungsten-clustering-8.0.4-132
```
The next step depends on your existing deployment:
- If you are upgrading a Multi-Site/Active-Active deployment:
  If you installed the original service by making use of the $CONTINUENT_PROFILES and $REPLICATOR_PROFILES environment variables, no further action needs to be taken to update the configuration information. Confirm that these variables are set before performing the validation and update.
  If you did not use these environment variables when deploying the solution, you must load the existing configuration from the current hosts in the cluster before continuing by using tpm fetch:
```
shell> ./tools/tpm fetch --hosts=east1,east2,east3,west1,west2,west3 \
  --user=tungsten --directory=/opt/continuent
```
  Important
  You must specify ALL the hosts within both clusters within the current deployment when fetching the configuration; use of the autodetect keyword will not collect the correct information.
- If you are upgrading any other deployment:
  If you are using the $CONTINUENT_PROFILES variable to specify a location for your configuration, make sure that the variable has been set correctly.
  If you are not using $CONTINUENT_PROFILES, a copy of the existing configuration must be fetched from the installed Tungsten Cluster installation:
```
shell> ./tools/tpm fetch --hosts=host1,host2,host3,autodetect \
  --user=tungsten --directory=/opt/continuent
```
  Important
  You must use the version of tpm from within the staging directory (./tools/tpm) of the new release, not the tpm installed with the current release.
  The current configuration information will be retrieved to be used for the upgrade:
```
shell> ./tools/tpm fetch --hosts=host1,host2,host3 --user=tungsten --directory=/opt/continuent
.......
NOTE  >> Configuration loaded from host1,host2,host3
```

Check that the update configuration matches what you expect by using tpm reverse:

shell> ./tools/tpm reverse
# Options for the dsone data service
tools/tpm configure dsone \
--application-password=password \
--application-port=3306 \
--application-user=app_user \
--connectors=host1,host2,host3 \
--datasource-log-directory=/var/log/mysql \
--install-directory=/opt/continuent \
--master=host1 \
--members=host1,host2,host3 \
'--profile-script=~/.bashrc' \
--replication-password=password \
--replication-port=13306 \
--replication-user=tungsten \
--start-and-report=true \
--user=tungsten

Run the upgrade process:

shell> ./tools/tpm update --replace-release

Note

During the update process, tpm may report errors or warnings that were not previously reported as problems. This is due to new features or functionality in different MySQL releases and Tungsten Cluster updates. These issues should be addressed and the tpm update command re-executed.

The following additional options are available when updating:

--no-connectors (optional)
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 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.

A successful update will report the cluster status as determined from each host in the cluster:

...........................................................................................................
Getting cluster status on host1
Tungsten Clustering 8.0.4 Build 132
connect to 'dsone@host1'
dsone: session established
[LOGICAL] /dsone > ls

COORDINATOR[host3:AUTOMATIC:ONLINE]

ROUTERS:
+----------------------------------------------------------------------------+
|connector@host1[31613](ONLINE, created=0, active=0)                      |
|connector@host2[27649](ONLINE, created=0, active=0)                      |
|connector@host3[21475](ONLINE, created=0, active=0)                      |
+----------------------------------------------------------------------------+

...

#####################################################################
# Next Steps
#####################################################################
We have added Tungsten environment variables to ~/.bashrc.
Run `source ~/.bashrc` to rebuild your environment.

Once your services start successfully you may begin to use the cluster.
To look at services and perform administration, run the following command
from any database server.

$CONTINUENT_ROOT/tungsten/tungsten-manager/bin/cctrl

Configuration is now complete.  For further information, please consult
Tungsten documentation, which is available at docs.continuent.com.

NOTE  >> Command successfully completed

The update process should now be complete. The current version can be confirmed by starting cctrl.