Table of Contents
Creating a Tungsten Cluster combines a number of different components, systems, and functionality, to support a running database dataservice that is capable of handling database failures, complex replication topologies, and management of the client/database connection for both load balancing and failover scenarios.
All deployments operate through the tpm command. tpm operates in two different modes:
tpm INI
configuration — tpm uses an
INI to configure the service on the
local host. The INI file must be
created on each host that will be part of the cluster.
tpm only manages the services on the local host; in a
multi-host deployment, upgrades, updates, and configuration must be
handled separately on each host.
tpm staging configuration — a tpm configuration is created by defining the command-line arguments that define the deployment type, structure and any additional parameters. tpm then installs all the software on all the required hosts by using ssh to distribute Tungsten Cluster and the configuration, and optionally automatically starts the services on each host. tpm manages the entire deployment, configuration and upgrade procedure.
Whilst the staging method of deployment is still available, it will be deprecated in a future release and therefore all new deployments should follow the INI method of deployment.
The following sections provide guidance and instructions for creating a number of different deployment scenarios using Tungsten Cluster.