Académique Documents
Professionnel Documents
Culture Documents
MySQL Advanced
MySQL Replication
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.
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.
MySQL Replication
setup
MySQL Master Turn on binary log and set the server id restart mysql server:
MySQL slave Set the master properties in /etc/mysql/my.cnf: server-id=2 master-user = rep_slave master-password = password replicate-do-db={db_name}
MySQL Replication
setup
MySQL Master Show master log position: mysql > show master status \G; File: mysql-bin.000011 Position: 784 Binlog_Do_DB: gaia_test MySQL slave Change log position: CHANGE MASTER TO MASTER_HOST=server_IP, MASTER_LOG_FILE=mysqlbin, MASTER_LOG_POS=784; Start Slave: mysql > slave start; See slave status and notice the SLAVE_* variables for errors (No = bad) : Show slave status\G;
Antnio Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09
MySQL Advanced
MySQL Cluster
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.
MySQL Cluster
MySQL cluster architecture consists of three types nodes:
Storage nodes:
SQL nodes: Management nodes:
MySQL Cluster
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
MySQL Cluster
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]
Antnio Amorim, Carlos Jesus. CU1 - DBWorkshop 9-10 /Feb/09
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
MySQL Cluster
Testing the installation:
bash$ ndb-mgm -e show
Connected to Management Server at: 127.0.0.1:1186 Cluster Configuration ---------------------
[ndbd(NDB)]
id=2
1 node(s)
[mysqld(API)] id=3
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');
| id
|
| name
MySQL Advanced
MySQL Partitioning
MySQL Partitioning
Partition types
RANGE partitioning: Assigns rows to partitions based on column values falling within a given range.
LIST partitioning: Similar to partitioning by range, except that the partition is selected based on columns matching one of a
Partitioning set of discrete values. HASH partitioning: A partition is selected based on the value returned by a user-defined expression that operates on column values in rows to be inserted into the table. The function may consist of any expression valid in MySQL that yields a nonnegative integer value. KEY partitioning: Similar to partitioning by hash, except that only one or more columns to be evaluated are supplied, and the MySQL server provides its own hashing function.
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 ) (
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) );
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;
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 (
PARTITIONS 4;
Q&A
For more information:
More on MySQL-cluster and other studies: SIM Studies at the GAIA WIKI The technical note: GAIA-C1-TN-SIM-CDJ-001-1.pdf GAIA-C1-TN-SIM-AAB-001-01.pdf
Antnio Amorim, Carlos Jesus. CU1 - First Database Testing Meeting, 20/Nov/08
MySQL Benchmarks
Test objectives
Past studies evaluated the architecture and performance of MySQL Cluster and PostgreSQL solutions for the Gaia Databases. MySQL Cluster:
MySQL-Cluster
PostgreSQL
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
Antnio Amorim, Carlos Jesus. CU1 - First Database Testing Meeting, 20/Nov/08
Antnio Amorim, Carlos Jesus. CU1 - First Database Testing Meeting, 20/Nov/08
Antnio Amorim, Carlos Jesus. CU1 - First Database Testing Meeting, 20/Nov/08