3.1. Deploying a Master/Slave Cluster

Within a master/slave service, there is a single master which replicates data to the slaves. The Tungsten Connector handles connectivity by the application and distributes the load to the datasources in the dataservice.

Figure 3.1. Topologies: Master/Slave Cluster

3.1.1. Prepare: Master/Slave Cluster

Before continuing with deployment you will need the following:

The name to use for the cluster.
The list of datasources in the cluster. These are the servers which will be running MySQL.
The list of servers that will run the connector.
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 Section 2.6, “Prepare Hosts” and Appendix B, Prerequisites for additional details.

3.1.2. Install: Master/Slave Cluster

Install the Tungsten Clustering package or download the Tungsten Clustering tarball, and unpack it:
```
shell> cd /opt/continuent/software
shell> tar zxf tungsten-clustering-5.3.6-24.tar.gz
```
Change to the Tungsten Clustering directory:
```
shell> cd tungsten-clustering-5.3.6-24
```
Run tpm to perform the installation, using either the staging method or the INI method. Review Section 9.1, “Comparing Staging and INI tpm Methods” for more details on these two methods.
Click the link below to switch examples between Staging and INI methods
Show Staging
Show INI
```
shell> ./tools/tpm configure defaults \
    --reset \
    --user=tungsten \
    --install-directory=/opt/continuent \
    --profile-script=~/.bash_profile \
    --replication-user=tungsten \
    --replication-password=password \
    --replication-port=13306 \
    --application-user=app_user \
    --application-password=secret \
    --application-port=3306 \
    --start-and-report=true

shell> ./tools/tpm configure alpha \
    --topology=clustered \
    --master=host1 \
    --members=host1,host2,host3 \
    --connectors=host4
```
```
shell> vi /etc/tungsten/tungsten.ini
```
```
[defaults]
user=tungsten
install-directory=/opt/continuent
profile-script=~/.bash_profile
replication-user=tungsten
replication-password=password
replication-port=13306
application-user=app_user
application-password=secret
application-port=3306
start-and-report=true

[alpha]
topology=clustered
master=host1
members=host1,host2,host3
connectors=host4
```
Configuration group defaults
The description of each of the options is shown below; click the icon to hide this detail:
Click the icon to show a detailed description of each argument.
- --reset
  reset
  For staging configurations, deletes all pre-existing configuration information between updating with the new configuration values.
- --user=tungsten
  user=tungsten
  System User
- --install-directory=/opt/continuent
  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
  profile-script=~/.bash_profile
  Append commands to include env.sh in this profile script
- --replication-user=tungsten
  replication-user=tungsten
  For databases that required authentication, the username to use when connecting to the database using the corresponding connection method (native, JDBC, etc.).
- --replication-password=password
  replication-password=password
  The password to be used when connecting to the database using the corresponding --replication-user.
- --replication-port=13306
  replication-port=13306
  The network port used to connect to the database server. The default port used depends on the database being configured.
- --application-user=app_user
  application-user=app_user
  Database username for the connector
- --application-password=secret
  application-password=secret
  Database password for the connector
- --application-port=3306
  application-port=3306
  Port for the connector to listen on
- --start-and-report=true
  start-and-report=true
  Start the services and report out the status after configuration
Configuration group alpha
The description of each of the options is shown below; click the icon to hide this detail:
Click the icon to show a detailed description of each argument.
- --topology=clustered
  topology=clustered
  Replication topology for the dataservice Valid values are star,cluster-slave,master-slave,fan-in,clustered,cluster-alias,all-masters,direct
- --master=host1
  master=host1
  The hostname of the master (extractor) within the current service. If the current host does not match this specification, then the deployment willby default be configured as a master/extractor.
- --members=host1,host2,host3
  members=host1,host2,host3
  Hostnames for the dataservice members
- --connectors=host4
  connectors=host4
  Hostnames for the dataservice connectors
Run tpm to install the software with the configuration.
```
shell > ./tools/tpm install
```
During 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 PATH and environment.

shell > source /opt/continuent/share/env.sh

Important

Do not include start-and-report if you are taking over for MySQL native replication. See Section 3.9.1, “Migrating from MySQL Native Replication 'In-Place'” for next steps after completing installation.

3.1.3. Best Practices: Master/Slave Cluster

Follow the guidelines in Section 2.5, “Best Practices”.

Prev	Up	Next
Chapter 3. Deployment: MySQL Topologies	Home	3.2. Deploying Multisite/Multimaster Clusters