1. MySQL Advanced MySQL Replication MySQL Cluster MySQL Partitioning António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

2. MySQL Advanced MySQL Replication António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

3. MySQL Replication Concepts MySQL replication tracks updates performed in a MySQL master logs and updates one or more slave servers. The mechanism involved in MySQL replication requires binary logging to be active. -Asynchronous replication, a slave doesn't need to be always active. -MySQL replication can be used to scale-out queries among different servers. -MySQL replication is a good solution for performing live backups. - Long distance data distribution. António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

4. MySQL Replication Architecture MySQL replication architecture: - Each update performed in a database is replicated from the master to the slaves. - Only slaves keep track of their replication status. - One may set at what point the replication begins. António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

7. MySQL Advanced MySQL Cluster António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

8. MySQL Cluster MySQL cluster is designed to provide near perfect availability through a shared nothing architecture, in turn this means that all the nodes in a MySQL cluster can be replicated for failover. MySQL cluster is a in memory database, which means that all data must be located in RAM, since version 5.1.6 a mechanism is available to store data on disk although Indexes must still fit in ram. All data in MySQL is horizontally partitioned, across different storage nodes, which means that all table data is split across the storage nodes. António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

9. MySQL Cluster MySQL cluster architecture consists of three types nodes: Storage nodes: All data is stored in this nodes. SQL nodes: Standard MySQL nodes, used for connection. Management nodes: Used to change the setup of the cluster. António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

10. MySQL Cluster António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09 Setup (Debian)‏ To setup a 3 node (API + engine + management) MySQL Cluster you must update 2 files: Edit /etc/mysql/my.cnf and add: [mysqld] ndbcluster [MYSQL_CLUSTER] ndb-connectstring=127.0.0. 1

11. MySQL Cluster António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09 Setup (debian) Create a new configuration file in /etc/mysql/ndb_mgmd.cnf: [ndbd default] NoOfReplicas=1 DataMemory=80M IndexMemory=18M [ndb_mgmd] Id=1 hostname=localhost datadir=/var/lib/mysql-cluster [mysqld]

12. MySQL Cluster Startup order: #1 Management nodes: invoke-rc.d mysql-ndb-mgm start (start-initial)‏ #2 Data nodes invoke-rc.d mysql-ndb start #3 SQL nodes invoke-rc.d mysql start António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

13. MySQL Cluster Testing the installation: bash$ ndb-mgm -e show Connected to Management Server at: 127.0.0.1:1186 Cluster Configuration --------------------- [ndbd(NDB)] 1 node(s)‏ id=2 @127.0.0.1 (Version: 5.1.22, Nodegroup: 0, Master)‏ [ndb_mgmd(MGM)] 1 node(s)‏ id=1 @127.0.0.1 (Version: 5.1.22)‏ [mysqld(API)] 1 node(s)‏ id=3 @127.0.0.1 (Version: 5.1.22)‏ António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

14. MySQL Cluster Testing the installation: mysql> create table person (id int, name varchar(32)) engine = ndb; Query OK, 0 rows affected (2,34 sec)‏ mysql> insert into person (id, name ) values ('11','carlos'); Query OK, 1 row affected (0,00 sec)‏ mysql> select * from person; +------+--------+ | id | name | +------+--------+ | 11 | carlos | +------+--------+ 1 row in set (0,00 sec)‏ António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

15. MySQL Advanced MySQL Partitioning António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

16. MySQL Partitioning c oncepts Typical SQL doesn't provide guidance to underling physical storage layer, Partitioning allows you to split a table across multiple files, through the usage of a special partitioning rule called partitioning function. Partitioning can only take place in engines that support partitioning, engines like MyISAM or InnoDB and not like CSV or BlackHole. The big performance boost in database partition is that partitions that do not satisfy a certain rule are not scanned, this is called partition pruning. António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

18. MySQL Partitioning examples Range partition: CREATE TABLE t1 ( r_name VARCHAR(50) NOT NULL, region_code TINYINT UNSIGNED NOT NULL )‏ PARTITION BY RANGE( region_code ) ( PARTITION p0 VALUES LESS THAN (64), PARTITION p1 VALUES LESS THAN (128), PARTITION p3 VALUES LESS THAN MAXVALUE ); António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

19. MySQL Partitioning examples List Partition: CREATE TABLE employees ( id INT NOT NULL, fname VARCHAR(30), lname VARCHAR(30), hired DATE NOT NULL DEFAULT '1970-01-01', separated DATE NOT NULL DEFAULT '9999-12-31', job_code INT, store_id INT )‏ PARTITION BY LIST(store_id) ( PARTITION pNorth VALUES IN (16,15,3,5,6,9,17), PARTITION pEast VALUES IN (1,2,8,10,11,19,20), PARTITION pWest VALUES IN (7, 4,12,13,14,18) ); António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

20. MySQL Partitioning examples Hash Partition: CREATE TABLE employees ( id INT NOT NULL, fname VARCHAR(30), lname VARCHAR(30), hired DATE NOT NULL DEFAULT '1970-01-01', separated DATE NOT NULL DEFAULT '9999-12-31', job_code INT, store_id INT )‏ PARTITION BY HASH(store_id)‏ PARTITIONS 5; António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

21. MySQL Partitioning examples Key Partition: CREATE TABLE k1 ( id INT NOT NULL PRIMARY KEY, name VARCHAR(20))‏ PARTITION BY KEY()‏ PARTITIONS 4; CREATE TABLE k1 ( id INT NOT NULL, name VARCHAR(20), UNIQUE KEY (id) )‏ PARTITION BY KEY()‏ PARTITIONS 4; António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

23. MySQL Benchmarks MySQL Single server MySQL Cluster Oracle António Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09

25. Single MySQL Server In order to pinpoint bottlenecks associated with MySQL, a series of basic tests were performed, these new tests made use of the available MDBExtractorIngestor package. Control and Monitor: Available at the local infrastructure was the SMS (Supervisor Monitor Scheduler) batch system, we deployed in one node the database and in another the Ingestor. At the local infrastructure was available the SMS (Supervisor Monitor Scheduler) batch system. The tests basic 2 node client server model the nodes where as following: Hardware setup António Amorim, Carlos Jesus. CU1 - First Database Testing Meeting, 20/Nov/08

26. MySQL Ingestor, Old and new JdbcObjectUpdater, 4.5Gb of data. Tests For MDBExtractorIngestor António Amorim, Carlos Jesus. CU1 - First Database Testing Meeting, 20/Nov/08 JdbcObjectUpdater.java

27. Oracle datapump (local), 1Gb of data. Tests For DbBenchmark António Amorim, Carlos Jesus. CU1 - First Database Testing Meeting, 20/Nov/08 JdbcObjectUpdater.java MySQL Ingestor, Old and new JdbcObjectUpdater, 1Gb of data.