Deployment of Composite Active/Active clusters is only supported using the INI method of deployment.
Configuration and deployment of the cluster works as follows:
Creates two basic Primary/Replica clusters.
Creates a composite service that includes the Primary/Replica clusters within the definition.
The resulting configuration within the example builds the following deployment:
One cluster, east, with three
hosts.
One cluster, west, with three
hosts.
All six hosts in the two clusters will have a manager, replicator and connector installed.
Each replicator has two replication services, one service that replicates the data within the cluster. The second service, replicates data from the other cluster to this host.
Creating the full topology requires a single install step, this creates the Tungsten Cluster cluster dataservices, and creates the Composite dataservices on different network ports to allow for the cross-cluster replication to operate.
Create the combined configuration file
/etc/tungsten/tungsten.ini on all cluster
hosts:
shell> vi /etc/tungsten/tungsten.ini[defaults] user=tungsten install-directory=/opt/continuent profile-script=~/.bash_profile replication-user=tungsten replication-password=secret replication-port=13306 application-user=app_user application-password=secret application-port=3306 rest-api-admin-user=apiuser rest-api-admin-pass=secret[east] topology=clustered master=east1 members=east1,east2,east3 connectors=east1,east2,east3[west] topology=clustered master=west1 members=west1,west2,west3 connectors=west1,west2,west3[usa] topology=composite-multi-master composite-datasources=east,west
Configuration group defaults
The description of each of the options is shown below; click the icon to hide this detail:
System User
install-directory=/opt/continuent
Path to the directory where the active deployment will be installed. The configured directory will contain the software, THL and relay log information unless configured otherwise.
profile-script=~/.bash_profile
Append commands to include env.sh in this profile script
For databases that required authentication, the username to use when connecting to the database using the corresponding connection method (native, JDBC, etc.).
The password to be used when connecting to the database using
the corresponding
--replication-user.
The network port used to connect to the database server. The default port used depends on the database being configured.
Database username for the connector
Database password for the connector
Port for the connector to listen on
rest-api-admin-user=apiuser
rest-api-admin-pass=secret
Configuration group east
The description of each of the options is shown below; click the icon to hide this detail:
Replication topology for the dataservice.
The hostname of the primary (extractor) within the current service.
Hostnames for the dataservice members
Hostnames for the dataservice connectors
Configuration group west
The description of each of the options is shown below; click the icon to hide this detail:
Replication topology for the dataservice.
The hostname of the primary (extractor) within the current service.
Hostnames for the dataservice members
Hostnames for the dataservice connectors
Configuration group usa
The description of each of the options is shown below; click the icon to hide this detail:
topology=composite-multi-master
Replication topology for the dataservice.
composite-datasources=east,west
Data services that should be added to this composite data service
The configuration above defines two clusters,
east and
west, which are both part of a
composite cluster service,
usa. Configuration can be
divided up into the four sections shown, as follows:
Service names should not contain the keyword
from within a
Composite Active/Active deployment. This keyword is used (with the
underscore separator, for example,
east_from_west
to denote cross-site replicators within the cluster. To avoid
confusion, avoid using from
so that it is easy to distinguish between replication pipelines.
When configuring this service, tpm will automatically imply the following into the configuration:
A parent composite service,
usa in this example, with
child services as listed,
east and
west.
Replication services between each child service, using the
service name
a_from_b,
for example,
east_from_west and
west_from_east.
More child services will create more automatic replication
services. For example, with three clusters,
alpha,
beta, and
gamma,
tpm would configure
alpha_from_beta and
alpha_from_gamma on the
alpha cluster,
beta_from_alpha and
beta_from_gamma on the
beta cluster, and so on.
For each additional service, the port number is automatically
configured from the base port number for the first service. For
example, using the default port 2112, the
east_from_west
service would have THL port 2113.
Execute the installation on each host within the entire composite cluster. For example, on all six hosts provided in the sample configuration above.
Install the Tungsten Cluster package (.rpm),
or download the compressed tarball and unpack it:
shell>cd /opt/continuent/softwareshell>tar zxftungsten-clustering-6.1.25-6.tar.gz
Change to the Tungsten Cluster staging directory:
shell> cd tungsten-clustering6.1.25-6Run tpm to install the Clustering software:
shell > ./tools/tpm install
During the installation and startup, tpm will notify you of any problems that need to be fixed before the service can be correctly installed and started. If the service starts correctly, you should see the configuration and current status of the service.
Initialize your PATH and environment:
shell> source /opt/continuent/share/env.sh
The Composite Active/Active clustering should be installed and ready to use.