This document provides an overview of installing a Tungsten cluster, including reviewing the cluster architecture and prerequisites, discussing installation methods, and demonstrating the installation process. It reviews decisions around the installation environment and Tungsten configuration. Key tools for controlling and monitoring the cluster like cctrl and trepctl are also introduced.

1. Basics : Simple Cluster Installation

2. Topics
In this short course we will:
• Review the Cluster Architecture
• Review prerequisites required
• Discuss installation Methods
– Staging vs INI
• Walkthrough an Installation (Full end to end demo)
• Recap Key Resources and Tools
Course Prerequisite Learning
– Basics: Introduction to Clustering
– Basics: The Power of the Connector
– Visit Continuent website or Tungsten University on YouTube to watch these recordings
2

3. Tungsten Cluster Architecture

4. Tungsten Cluster Architecture
4

5. Cluster Decisions and Prerequisites

6. Pre Installation Environment Decisions
• Where will the connectors be installed?
– Dev/Test/Staging – On DB Host is OK
– Production – Dedicated hosts or hosted with App Servers
• Which release of MySQL?
– MySQL Community
– Percona
– MariaDB
– Oracle MySQL Enterprise
• Which version?
– 5.7 caveats
• What monitoring tools do you have?
• What backup tools do you have?
6

7. Prerequisities
• Review docs
– http://docs.continuent.com/tungsten-clustering-5.2/prerequisite.html
• Host Prerequisites
– OS user
– /etc/hosts
– sudoers and ssh
– Ruby
– Java
• Network Prerequisites
– Review port requirements
• MySQL Prerequisites
– my.cnf settings
– tungsten user accounts
7

8. Pre Installation Tungsten Decisions
• TAR file or RPM?
• INI-based install or staging install?
• Which connector mode?
– Bridge is default
– Proxy mode
– SmartScale
• SSL Enabled?
8

9. Installation Methods: ini vs staging
• INI-based Install
– Install managed via /etc/tungsten/tungsten.ini on EACH host
– PROS
• Control over each node individually
• Easy integration to automation software such as puppet and chef
• Remove dependency on single host for install
– CONS
• Configuration changes must be performed individually
• Risk of misconfiguration between nodes
9

10. Installation Methods: ini vs staging
• Staging Install
– Install managed from one host
– Could be a cluster node or a separate host outside of cluster
– PROS
• One single place for configuration
• Easy to install/update entire cluster in one go
• Cluster configuration applied to all nodes, less risk of misconfiguration
– CONS
• No easy integration to automation software
• Staging host become single point of failure for configuration management
– Especially important if Staging host is a DB Node
10

11. Installation Demo

12. Command Line Tools
&
Resources

13. Tools : cctrl
13
• “cctrl” can be run from any node within a cluster to control the cluster and gather information
• Type “help” to get a full list of all commands available
• “ls” provides a summary overview of the entire cluster
[LOGICAL] /east > ls
COORDINATOR[db1:AUTOMATIC:ONLINE]
ROUTERS:
+----------------------------------------------------------------------------+
|connector@db1.chris-vagrant[10518](ONLINE, created=0, active=0) |
|connector@db2.chris-vagrant[10596](ONLINE, created=0, active=0) |
|connector@db3.chris-vagrant[10541](ONLINE, created=0, active=0) |
+----------------------------------------------------------------------------+
DATASOURCES:
+----------------------------------------------------------------------------+
|db1(master:ONLINE, progress=0, THL latency=0.680) |
|STATUS [OK] [2017/06/22 03:04:15 PM UTC] |
+----------------------------------------------------------------------------+
| MANAGER(state=ONLINE) |
| REPLICATOR(role=master, state=ONLINE) |
| DATASERVER(state=ONLINE) |
| CONNECTIONS(created=0, active=0) |
+----------------------------------------------------------------------------+
+----------------------------------------------------------------------------+
|db2(slave:ONLINE, progress=0, latency=3.913) |
|STATUS [OK] [2017/06/22 03:04:18 PM UTC] |
+----------------------------------------------------------------------------+
| MANAGER(state=ONLINE) |
. . .

14. Tools : trepctl
14
• “trepctl status” can be run from any node within a cluster to view the status of the local
replicator
• “trepctl status –r 3” will show status output refreshed every 3 second until CTRL+C
• “trepctl qs” provides a quick summary overview of the local replicator
• “trepctl perf” provides deeper diagnostics of the different stages in the replicators
$ trepctl qs
State: east Online for 21.069s, running for 45.654s
Latency: 0.837s from DB commit time on db1 into THL
21.839s since last database commit
Sequence: 1 last applied, 0 transactions behind (0-1 stored) estimate 0.00s before synchronization

15. Tools : tpm connector
15
• Simple and quick way to connect to MySQL CLI
• Tungsten Commands to query database and cluster stats
– Connector-based Tungsten commands are NOT available in Bridge Mode
– This is a good way to tell if you are in Bridge mode – if no commands are available, then you are in Bridge mode
– `tungsten help` will show all commands available
mysql> tungsten help;
+---------------------------------------------------------------------------------------------------------------------------------+
| Message |
+---------------------------------------------------------------------------------------------------------------------------------+
| tungsten connection status: display information about the connection used for the last request ran |
| tungsten connection count: gives the count of current connections to each one of the cluster datasources |
| tungsten cluster status: prints detailed information about the cluster view this connector has |
| tungsten show [full] processlist: list all running queries handled by this connector instance |
| tungsten show variables [like '<string>']: list connector configuration options in use. The <string> may contain '%' wildcards |
| tungsten flush privileges: reload user.map and refresh user credentials |
| tungsten mem info: display memory information about current JVM |
| tungsten gc: calls garbage collector |
| tungsten help: display this help message |
+---------------------------------------------------------------------------------------------------------------------------------+
9 rows in set (0.00 sec)

16. Log Files
16
• The /opt/continuent/service_logs/ directory contains both text files and symbolic links.
• Links in the service_logs directory go to one of three (3) subdirectories:
– /opt/continuent/tungsten/tungsten-connector/log/
– /opt/continuent/tungsten/tungsten-manager/log/
– /opt/continuent/tungsten/tungsten-replicator/log/
tungsten@db1:/opt/continuent/service_logs $ ll
total 116
lrwxrwxrwx 1 tungsten tungsten 61 Jun 22 09:52 connector.log -> /opt/continuent/tungsten/tungsten-connector/log/connector.log
lrwxrwxrwx 1 tungsten tungsten 62 Jun 22 09:52 mysqldump.log -> /opt/continuent/tungsten/tungsten-replicator/log/mysqldump.log
lrwxrwxrwx 1 tungsten tungsten 55 Jun 22 09:52 tmsvc.log -> /opt/continuent/tungsten/tungsten-manager/log/tmsvc.log
lrwxrwxrwx 1 tungsten tungsten 60 Jun 22 09:52 trepsvc.log -> /opt/continuent/tungsten/tungsten-replicator/log/trepsvc.log
lrwxrwxrwx 1 tungsten tungsten 63 Jun 22 09:52 xtrabackup.log -> /opt/continuent/tungsten/tungsten-replicator/log/xtrabackup.log

17. Next Steps
• If you are interested in knowing more about the clustering software and would like to try it out for
yourself, please contact our sales team who will be able to take you through the details and
setup a POC – sales@continuent.com
• Read the documentation at http://docs.continuent.com/tungsten-clustering-5.2/index.html
• Subscribe to our Tungsten University YouTube channel! http://tinyurl.com/TungstenUni
• Visit the events calendar on our website for upcoming Webinars and Training Sessions
17

18. For more information, contact us:
Eric Stone
COO
eric.stone@continuent.com
MC Brown
VP Products
mc.brown@continuent.com
Chris Parker
Director, Professional Services EMEA & APAC
chris.parker@continuent.com
Eero Teerikorpi
Founder, CEO
eero.teerikorpi@continuent.com
+1 (408) 431-3305