Has MySQL grown up?

Has MySQL Grown Up? Mark Stanton grude

A brief history

A brief history1995 Named after Monty’s daughter (My)2000 Open sourced2001 3.232003 4.02005 5.0 Oracle buys the company behind InnoDB2006 MySQL hits 33% market share, Oracle tries to buy2008 5.1 Sun acquires MySQL for $1 billion, Monty leaves2010 5.5 Oracle buys Sun for $7.4 billion

Where are we now?• MySQL is growing up• Oracle are showing love• Facebook, Google & others are contributing• Make sure you are running: • 5.5 • recent version of 5.1

The wonderful world of Storage Engines

Storage Engines• Storage engines are pluggable table types• You can have multiple storage engines within each a DB• Transparent to clients (mostly) MyISAM InnoDB

MyISAM• Simple, light weight• File based• FULLTEXT indexes• Table level locking

InnoDB• ACID compliant • Hot backup• Crash safe • Active development• Foreign keys • Optimised for multi-core• Row-level locking • Default from 5.5 on• Table compression • No FULLTEXT (until 5.6)

NDB - MySQL Cluster• High Availability• Tables clustered across nodes• Auto fail & recover• Auto partitioning• No FK, limited transactions• Poor multi-table joins• Pretends to be MySQL, really whole other product

Other Storage Engines• MERGE• MEMORY• BLACKHOLE• CSV ( ) CREATE TABLE export ENGINE=CSV SELECT foo, bar FROM table

Storage Engines: Conclusion• InnoDB is the new default & new direction• MyISAM is the past• If you are still on MyISAM, think of moving• NDB is very interesting for special cases

Replication

Why Replicate?• Scale out• High availability• Geographic• Backup• Analytics / Business Intelligence

Under the Hood: Logs IO Thread Step 2 Step 3 SQL ThreadStep 1 Step 4

Under the Hood: Format • Statement: UPDATE table.. • Records 1100101100111

Under the Hood: Semi-sync Step 1 Step 1Step 1 Step 2

Conﬁguration: Master-Slave• Master my.cnf: server-id = 10 log-bin=mysql-M1-bin• Master DB: mysql> CREATE USER repl; Name Server-Id Port mysql> GRANT REPLICATION SLAVE ON *.* TO repl; M1 10 3310• Slave my.cnf: server-id = 11 M1-S1 11 3311• Slave DB: mysql> CHANGE MASTER TO MASTER_HOST=localhost, MASTER_PORT=3310, MASTER_USER=repl;

SHOW SLAVE STATUSmysql> show slave status G*************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Server_Id: 10 Master_Host: localhost Master_Port: 3310 Master_User: repl Master_Log_File: mysql-M1-bin.000017 Read_Master_Log_Pos: 107 Exec_Master_Log_Pos: 107 Slave_IO_Running: Yes Slave_SQL_Running: Yes Last_Errno: 0 Last_Error: Seconds_Behind_Master: 0 Master_Server_Id: 10

In Practice

Multi-Master M1 M2 M1#S1 M2#S1

Why Multi-Master?• Active/Passive sites• High Availability• Geographically dispersed writes

Multi-Master: ConsiderationsMulti-Master replication needs at least one of:• Conﬂict Avoidance• Conﬂict Resolution• Hope

Multi-Master: Considerations• Conﬂict Avoidance • UUIDs • Auto increment hacks = 2 auto_increment_increment auto_increment_offset = 1 • Semi-sync • Active/Passive • Ticket server

Multi-Master: Considerations• Conﬂict Resolution • Cluster/NDB • Galera • or roll your own...

Conﬁguration: Multi-MasterName Server-Id PortM1 10 3310M1-S1 11 3311M2 20 3320 M1 M2M2-S1 21 3321• M2 as slave of M1• M1 as slave of M2• M2-S1 as slave of M2 M1#S1 M2#S1

Review of Topologies Master Master Master Master Master Master Slave Slave Slave Slave Master Slave Master Master Mul)* Mul)*Mul$% Slaves SlavesSlaves

Connector/J• MySQL’s Connector/J supports: • Failover • Load Balancing • (Replication)

JDBC Connection Syntaxjdbc:mysql://hostname:port/dbname ?property=valuejdbc:mysql://localhost:3306/test?username=root

JDBC Failoverjdbc:mysql://host1:port1,host2:port2/dbname

JDBC Load Balancingjdbc:mysql:loadbalance://host1:port1,host2:port2,host3:port3/dbname

Warning• Failover doesn’t attempt to be transparent• ColdFusion doesn’t allow you full control• Check/upgrade your Connector/J version• Set connectionTimeout, socketTimeout and blacklistTimeout carefully

MySQL Enterprise Monitor

MySQL Enterprise Monitor• Heat maps• Charts• Query analyser• Replication status• Conﬁgurable advisors & email alerts• Event logs

MySQL Enterprise Monitor• Server with agents for each mysqld• Query analyser can have performance hit• Non-free

Backing Up MySQL• Several approaches: • Copy DB ﬁles • mysqldump • binlog • Backup to slave • mysqlbackup

Backup: File copy• Enable read lock: mysql> LOCK TABLES READ; mysql> FLUSH TABLES;• Run ﬁle copy: $ cp -R ./myDB /mybackups/myDB• Unlock tables: mysql> UNLOCK TABLES;

Backup: mysqldump• Creates an sql script containing commands to recreate database• Run from command-line: $ mysqldump --single-transaction --all-databases > backup_sunday_1_PM.sql

Backup: binlog• The binary log: • records statements • can be replayed from arbitrary point • need to know where to replay from• Rotate binlog mysql> FLUSH LOGS;• Then copy relevant ﬁles

Backup: Slave• Setup dedicated slave for backup purposes• Shutdown slave• Run backup• Restart slave

Backup: mysqlbackup• Non-free enterprise backup tool• Features: • Hot • Incremental • Compressed • Veriﬁcation

Summary of Backup Options backup to copy DB ﬁles mysqldump binlog mysqlbackup slave Lock (MyISAM) Lock (MyISAM)Hot/Read-Lock Lock Hot Hot Hot* (InnoDB) Hot (InnoDB)Incremental No No Yes No YesInnoDB Support No Yes Yes Yes YesRestore Speed Fast OK ** OK Fast Fast* use --single-transaction for InnoDB** disable for autocommit/FK checks in InnoDB

Questions?• Mark Stanton• http://blog.gruden.com• mark@gruden.com• @MarkStanto

Has MySQL grown up?

by Mark Stanton on Nov 16, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 1

Statistics

Has MySQL grown up? — Presentation Transcript