Use the tpm update command to upgrade to the latest version.
shell>cd /opt/continuent/softwareshell>tar zxf tungsten-clustering-7.0.3-141.tar.gzshell>cd tungsten-clustering-7.0.3-141shell>./tools/tpm update --replace-release
The use of --replace-release is not mandatory for minor configuration changes.
however it is highly recommended when upgrading between versions.
Using this option will ensure that underlying metadata and property files are cleanly rebuilt, thus ensuring any new or deprecated properties between releases are correctly added/removed acordingly.
After unpacking the new software into the staging directory, the
tpm update command will read the
tungsten.ini configuration and install the new
software. All services will be stopped and the new services will be
started.
The tpm update command may cause a brief outage while restarting the connectors. This will occur if you are upgrading to a new version You can avoid that with:
shell> ./tools/tpm update dataservice --no-connectorsThe connectors must be updated separately on each server by running:
shell> tpm promote-connector
During the lifetime of the cluster, switches may happen and the current
Primary may well be a different node than what is reflected in the static
ini file in the master= line. Normally, this difference
is ignored during an update or an upgrade.
However, if a customer has some kind of procedure (i.e. automation) which
hand-edits the ini configuration file master= line at
some point, and such hand-edits do not reflect the current reality at the
time of the update/upgrade, an update/upgrade will fail and the cluster
may be left in an indeterminate state.
The best practice is to NOT change the master= line
in the INI configuration file after installation.
There is still a window of opportunity for failure. The update will
continue, passing the CurrentTopologyCheck test and
potentially leaving the cluster in an indeterminate state if the
master= option is set to a hostname that is not the
current Primary or the current host.