Tungsten Cluster supports the creation of composite clusters. This includes multiple active/passive dataservices tied together. One of the dataservices is identified as the active, containing the Primary node and all other dataservices (passive) replicate from it.
Before continuing with deployment you will need the following:
The cluster name for each Active/Passive Cluster and a Composite cluster name to group them.
The list of datasources in each cluster. These are the servers which will be running MySQL.
The list of servers that will run the connector. Each connector will be associated with a preferred cluster but will have access to the Primary regardless of location.
The username and password of the MySQL replication user.
The username and password of the first application user. You may add more users after installation.
All servers must be prepared with the proper prerequisites. See Appendix B, Prerequisites for additional details.
Install the Tungsten Cluster package or download the Tungsten Cluster tarball, and unpack it:
shell>
cd /opt/continuent/softwareshell>tar zxftungsten-clustering-6.1.25-6.tar.gzChange to the Tungsten Cluster directory:
shell>
cdtungsten-clustering-6.1.25-6Run tpm to perform the installation. This method assumes you are using the Section 10.3, “tpm Staging Configuration” method:
Click the link below to switch examples between Staging and INI methods
shell>
./tools/tpm configure defaults \ --reset \ --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=secretshell>./tools/tpm configure alpha \ --topology=clustered \ --master=host1.alpha \ --members=host1.alpha,host2.alpha,host3.alpha \ --connectors=host1.alpha,host2.alpha,host3.alphashell>./tools/tpm configure beta \ --topology=clustered \ --relay=host1.beta \ --members=host1.beta,host2.beta,host3.beta \ --connectors=host1.beta,host2.beta,host3.beta \ --relay-source=alphashell>./tools/tpm configure gamma \ --composite-datasources=alpha,betashell>
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[alpha] topology=clustered master=host1.alpha members=host1.alpha,host2.alpha,host3.alpha connectors=host1.alpha,host2.alpha,host3.alpha[beta] topology=clustered relay=host1.beta members=host1.beta,host2.beta,host3.beta connectors=host1.beta,host2.beta,host3.beta relay-source=alpha[gamma] composite-datasources=alpha,betaConfiguration group
defaultsThe description of each of the options is shown below; click the icon to hide this detail:
For staging configurations, deletes all pre-existing configuration information between updating with the new configuration values.
System User
--install-directory=/opt/continuentinstall-directory=/opt/continuentPath 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_profileprofile-script=~/.bash_profileAppend 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
Optional: Must be specified along with rest-api-admin-pass if you wish to access the full API features and use the Dashboard GUI for cluster installations.rest-api-admin-user=apiuser--rest-api-admin-pass=secret
Optional: Must be specified along with rest-api-admin-user if you wish to access the full API features.rest-api-admin-pass=secret
Configuration group
alphaThe 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.
--members=host1.alpha,host2.alpha,host3.alphamembers=host1.alpha,host2.alpha,host3.alphaHostnames for the dataservice members
--connectors=host1.alpha,host2.alpha,host3.alphaconnectors=host1.alpha,host2.alpha,host3.alphaHostnames for the dataservice connectors
Configuration group
betaThe 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.
--members=host1.beta,host2.beta,host3.betamembers=host1.beta,host2.beta,host3.betaHostnames for the dataservice members
--connectors=host1.beta,host2.beta,host3.betaconnectors=host1.beta,host2.beta,host3.betaHostnames for the dataservice connectors
Dataservice name to use as a relay source
Configuration group
gammaThe description of each of the options is shown below; click the icon to hide this detail:
--composite-datasources=alpha,betacomposite-datasources=alpha,betaData services that should be added to this composite data service
Run tpm to install the software with the configuration.
shell >
./tools/tpm installDuring the startup and installation, 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
PATHand environment.shell >
source /opt/continuent/share/env.sh
The Composite Active/Passive Cluster should be installed and ready to use.
Follow the guidelines in Section 2.5, “Best Practices”.