Tungsten Clustering is available in a number of different distribution types, and
the methods for configuration available for these different packages
differs. See Section 9.1, “Comparing Staging and
tpm Methods” for more
information on the available installation methods.
|tpm Command-line Configuration||Yes||Yes|
|tpm INI File Configuration||Yes||Yes|
|Deploy Entire Cluster||Yes||No|
|Deploy Per Machine||No||Yes|
Two primary deployment sources are available:
Using the RPM/DEB package format is more suited to using the INI file format, as hosts can be installed and upgraded to the latest RPM/DEB package independently of each other.
All packages are named according to the product, version number, build release and extension. For example:
The version number is
6.1.3 and build
numbers indicate which build a particular release version is based on, and
may be useful when installing patches provided by support.
To use the TAR/GZipped packages, download the files to your machine and unpack them:
tar zxf tungsten-replicator-6.1.3-37.tar.gz
This will create a directory matching the downloaded package name,
version, and build number from which you can perform an install using
either the INI file or command-line configuration. To use, you will need
to use the tpm command within the
tools directory of the extracted package:
The RPM and DEB packages can be used for installation, but are primarily designed to be in combination with the INI configuration file.
Installing the RPM or DEB package will do the following:
tungsten system user
if it doesn't exist
tungsten system user
part of the
mysql group if it
Unpack the software into
$REPLICATOR_PROFILES environment variables
Update the profile script to include the
Although the RPM/DEB packages complete a number of the pre-requisite steps required to configure your cluster, there are additional steps, such as configuring ssh, that you still need to complete. For more information, see Appendix B, Prerequisites.
By using the package files you are able to setup a new server by creating
/etc/tungsten.ini file and then installing the
package. Any output from the tpm command will go to
If you download the package files directly, you may need to add the signing key to your environment before the package will load properly.
rpm --import http://www.continuent.com/RPM-GPG-KEY-continuent
For Ubuntu/Debian platforms, the gpg command is used :
gpg --keyserver keyserver.ubuntu.com --recv-key 7206c924
To obtain the package files, you can use one of the following methods:
Download from an existing download page.
rpm -i http://releases.continuent.com.s3.amazonaws.com/replicator-release-stable-0.0-1.x86_64.rpm
For nightly builds:
rpm -i http://releases.continuent.com.s3.amazonaws.com/replicator-release-nightly-0.0-1.x86_64.rpm
For Ubuntu/Debian packages:
echo "deb http://apt.tungsten-replicator.org/ stable main" \ >/etc/apt/sources.list.d/tungsten_stable.list
Nightly builds are also available:
echo "deb http://apt-nightly.tungsten-replicator.org/ nightly main" \ >/etc/apt/sources.list.d/tungsten_nightly.list
Then update your apt repository:
Once an INI file has been created and the packages are available, the installation can be completed using:
On RHEL/CentOS/Amazon Linux:
yum install tungsten-replicator
apt-get install tungsten-replicator
If you upgrade to a new version of the RPM or DEB package it will do the following:
The tpm update will restart all Continuent Tungsten services so you do not need to do anything after upgrading the package file.