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 Section 9.2, “Processing Installs and Upgrades”. The behavior of tpm update is dependent on two factors.
Are you upgrading to a new version or applying configuration changes to the current version?
The installation method used during deployment.
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
An installation based on an INI file may include this line but there
will be an
/etc/tungsten/tungsten.ini file on each
Upgrading to a new version
If a staging directory was used; see Section 9.3.6, “Upgrades from a Staging Directory”.
If an INI file was used; see Section 9.4.3, “Upgrades with an INI File”
Applying configuration changes to the current version
If a staging directory was used; see Section 9.3.7, “Configuration Changes from a Staging Directory”.
If an INI file was used; see Section 9.4.4, “Configuration Changes with an INI file”.
Special Considerations for the Connector
As of software version 4.0.0, the tpm command will use connector graceful-stop 30 followed by connector start (in [Tungsten Clustering (for MySQL) 6.1 Manual]) when upgrading versions. If that command fails then a regular connector stop (in [Tungsten Clustering (for MySQL) 6.1 Manual]) is run.
This behavior is also applied when using tools/tpm update --replace-release.
The use of connector reconfigure (in [Tungsten Clustering (for MySQL) 6.1 Manual]) is disabled for the following:
--application-port --application-readonly-port --router-gateway-port --router-jmx-port --conn-java-mem-size