The tpm update also allows you to apply any
configuration changes. Start by making any necessary changes to the
tungsten.ini file. Then proceed to running
tpm update.
shell>cd /opt/continuent/tungstenshell>./tools/tpm update
If you configured the profile-script option
in your INI file, then the environment will be configured with aliases and
PATHS set, therefore you can also simply execute:
shell> tpm updateIf you are making significant changes such as adding/removing nodes or you are changing hostnames, then it is recommended to execute the update from tjhe software staging path to ensure all metadata files are updated correctly, for example:
shell>cd /opt/continuent/software/tungsten-clustering-7.0.3-141shell>./tools/tpm update --replace-release
This will read the tungsten.ini file and apply the
settings. The tpm command will identify what services
likely need to be restarted and will just restart those. You can manually
restart the desired services if you are unsure if the new configuration
has been applied.
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 --replace-release --no-connectorsAfterwards, the connectors must still be restarted on each server to pick up the new version or any changes, this can be done when convenient, by running:
shell> tpm promote-connector