The tpm command is designed to simplify the deployment activity across all hosts in a dataservice. These operations can be executed on each host in parallel to speed up the process. The general processis as follows:
Validate the configuration settings
Each host will validate the configuration based on validation classes. This will do things like check file permissions and database credentials. If errors are found during this stage, they will be summarized and the script will exit.
##################################################################### # Validation failed ##################################################################### ##################################################################### # Errors for host3 ##################################################################### ERROR >> host3 >> Password specified for app@% does not match the running instance on » tungsten@host3:13306 (WITH PASSWORD). This may indicate that the user has a password » using the old format. (MySQLConnectorPermissionsCheck) ##################################################################### # Errors for host2 ##################################################################### ERROR >> host2 >> Password specified for app@% does not match the running instance on » tungsten@host2:13306 (WITH PASSWORD). This may indicate that the user has a password » using the old format. (MySQLConnectorPermissionsCheck) ##################################################################### # Errors for host1 ##################################################################### ERROR >> host1 >> Password specified for app@% does not match the running instance on » tungsten@host1:13306 (WITH PASSWORD). This may indicate that the user has a password » using the old format. (MySQLConnectorPermissionsCheck)
At this point you should verify the configuration settings and retry the
tpm install command. It is always advisable to understand
and fix any errors that occur, but should you wish to ignore them, you can skip them
by adding the skip-validation-check=ChecktoSkip. When
re-running the tpm install command this check will be
bypassed. The names of the checks are always displayed as part of the error in
paranthesis, for example, the above error is fired by the validation check called
MySQLConnectorPermissionsCheck
A full list of the validation checks can be viewed at Section 9.7, “tpm Validation Checks”
Deploy and write configuration files
If validation is successful, we will move on to deploying and writing the actual configuration files. The tpm command uses a JSON file that summarizes the configuration. The Tungsten processes use many different files to store the configuration and tpm is responsible for writing them.
The /opt/continuent/releases directory will start
to collect multiple directories after you have run multiple upgrades. We
keep the previous versions in case a downgrade is
needed or for review at a later date. If your upgrade has been
successful, you can remove old directories using the clean_release_directory
command. If you remove them manually, make sure you do not remove the directory that is linked to by the
/opt/continuent/tungsten symlink as this is the current active release.
Do not change configuration files by hand other than the /etc/tungsten/tungsten.ini. This will
cause future updates to fail. One of the validation checks compares
the file that tpm has written with the current file. If
there are differences, validation will fail.
This is done to make sure that any configuration changes made by hand are not wiped out without giving you a chance to save them. You can run tpm query modified-files to see what, if any, changes have been made.
Start Tungsten services
After the installation is fully configured, the tpm
command will start services on all of the hosts if the tpm
option start or
start-and-report was set. This process is
slightly different depending on if you are doing a clean install or and
upgrade.
Install
Check if --start or
--start-and-report were
provided in the configuration
Start Tungsten Replicator on all hosts
Upgrade
Stop the Tungsten Replicator on all nodes