Skip to main content
Common Reference

tpm update

The tpm update command is used when applying configuration changes or upgrading to a new version. The process is designed to be simple and maintain availability of all services. The actual process will be performed as described in "Processing Installs and Upgrades". The behavior of tpm update is dependent on two factors.

  1. Are you upgrading to a new version or applying configuration changes to the current version?
  2. The installation method used during deployment.
note

Check the output of tpm query staging to determine which method your current installation uses. The output for an installation from a staging directory will start with

# Installed from
tungsten@staging-host:/opt/continuent/software/tungsten-clustering-8.0.4-132

An installation based on an INI file will also include the line:

# Configuration built from /etc/tungsten/tungsten.ini

Upgrading to a new version​

Applying configuration changes to the current installation​

For Tungsten Clustering Users

During the update process, the cluster will be in MAINTENANCE mode. This is intentional to prevent unwanted failovers during the proces, however it is important to understand that should the primary fail for genuine reasons NOT associated with the upgrade, then failover will also not happen at that time.

It is important to ensure clusters are returned to the AUTOMATIC state as soon as all Maintenance operations are complete and the cluster is stable.

Special Considerations for the Connector​

Applies to: Tungsten Clustering for MySQL

The tpm command will use connector graceful-stop 30 followed by connector start when upgrading versions. If that command fails then a regular connector stop is run.

This behavior is also applied when using tools/tpm update --replace-release.

The tpm command will use connector reconfigure when changing connector settings without a version upgrade.

The use of connector reconfigure is disabled if any of the following properties are set:

application-port
application-readonly-port
router-gateway-port
router-jmx-port
conn-java-mem-size

If connector reconfigure can't be used, connector graceful-stop 30 and connector start are used.

To avoid connectors being restarted as part of this process, you should also include the --no-connectors option.

You will then need to manually restart the connectors or use the tpm promote-connector when convenient.