!

"#$%
&'()*+,-*./012-.3*,)

Lars Thalmann
Technical lead
Replication, Backup, and Engine Technology

Mats Kindahl
Lead Developer
Replication Technology

MySQL Conference and Expo 2008

4./+'(-5
 !

!"#$%0&'()*+,-*./
67"8 9.:8

1. High Availability Snapshots (Backup)

Possibility of fail-over 1. Client program mysqldump
2. Load-balancing/Scale- With log coordinates
out 2. Using backup
Query multiple servers InnoDB, NDB
3. Off-site processing
Don’t disturb master
Binary log
1. Replication
Asynchronous pushing to slave
2. Point-in-time recovery
Roll-forward
 1'3;*/.).<"
Master MySQL Server
• Changes data
• Has binlog turned on Master
• Pushes binlog events to slave after slave has requested them MySQL
Server

Slave MySQL Server

• Main control point of replication
• Asks master for replication log Replication
• Gets binlog event from master

MySQL
Binary log Server
• Log of everything executed Slave
• Divided into transactional components
• Used for replication and point-in-time recovery
 1'3;*/.).<"

Synchronous replication Master

• A transaction is not committed until the data MySQL
has been replicated (and applied) Server
• Safer, but slower
• This is available in MySQL Cluster
Replication
Asynchronous replication
• A transaction is replicated after it has been
committed MySQL
Server
• Faster, but you can in some cases loose
transactions if master fails Slave
• Easy to set up between MySQL servers
4./=*<23*/<
&'()*+,-*./
&'>2*3'?0+./=*<23,-*./0@ ;"A+/=
! Replication Master
log-bin
server_id
! Replication Slave
server_id
B(-*./,)0*-';50*/0;"A+/=0@ 67,-0-.03'()*+,-'8
! Replication Master
binlog-do-db
binlog-ignore-db
! Replication Slave
replicate-do-db, replicate-ignore-db
replicate-do-table, replicate-ignore-table
replicate-wild-do-table
replicate-wild-ignore-table
!.3'0.(-*./,)0+./=*<23,-*./0./0-7'05),C'
! read-only
! log-slave-updates
! skip-slave-start
4./=*<23,-*./0@ <3,/-50./0;,5-'3

GRANT REPLICATION SLAVE on *.*

TO ‘rep_user’@’slave-host’
IDENTIFIED BY ‘this-is-the-password’
9.:0-.0?'()."03'()*+,-*./

#-'(0DE0!,F'0,0G,+F2(0.=0-7'0;,5-'3

Master

Either an “offline backup”

or an “online backup”...
4./=*<23,-*./0@ H..?0,?C*+'
! Start the binary log on the master immediately following the
backup. e.g.:
Make the GRANTs on the master server
Shut down mysqld on the master server
Edit my.cnf
Make the backup
Restart mysqld on the master
! Do not try to configure master_host, etc. in my.cnf on the
slave.
(this is still allowed, but it was always a bad idea)
&'5-.3'0-7'0G,+F2(0./-.0-7'05),C'

Master

Slave
4./=*<23'0-7'05),C'E0(,3-0D

CHANGE MASTER TO
Master
master_host = “dbserv1”,
master_user = “rep-user”,
master_password =
“this-is-the-password”;

Slave
4./=*<23'0-7'05),C'E0(,3-0I

CHANGE MASTER TO
Master
master_host = “dbmaster.me.com”,
master_log_file = “binlog-00001”,
master_log_pos = 0;

Slave
#-,3-0-7'05),C'J

Master

Slave START SLAVE;

&'()*+,-*./
1.(.).<*'5
!,5-'30:*-70#),C'

Master

Slave
!,5-'30:*-70#),C'
binary
log
Master

TCP connection

Slave
&'()*+,-*./0*50*/?'('/?'/-0.=0#-.3,<'0K/<*/'5
! You can replicate between any pair of engines
InnoDB to InnoDB
MyISAM to MyISAM
InnoDB to MyISAM
MEMORY to MyISAM
etc...
! The binary log is not the InnoDB transaction log (or the
Falcon log, or ...)
!,5-'30:*-70!,/"0#),C'5

Master

Slave Slave Slave Slave

47,*/

Master/
Master Slave
Slave

log_slave_updates = 1
47,*/00@ #'3C'30I0<.'50?.:/AAA0

Master
X
Master/
Slave
Slave
AAA0#'3C'30L0*505-*))02(M0G2-0.2-0.=05"/+

Master
X
Master/
Slave
Slave
 K,+705'3C'307,50,02/*>2'0N5'3C'3O*?P

server_id=1 server_id=3
Master/
Master Slave
Slave

server_id=2

... and every event in a binary log file contains the

server id number of the server where the event
originated.
&*/<
server_id=2
Master/
Slave

Master/
Slave

server_id=1 Master/
Slave

server_id=3
17'03*/<0-.(.).<"0*50/.-0,03'+.;;'/?'?0
+./=*<23,-*./
Master/
Slave

Master/
Slave

X
Master/
Slave
 Q,*30.=0!,5-'35

Master/ Master/
Slave Slave

The pair is a “special case” of the ring topology used

for
high availability.
17'0-:.0;.5-0+.;;./0-.(.).<*'5
=.30!"#$%0&'()*+,-*./

Master

Master/ Master/
Slave Slave

Slave
Slave

Slave
17'0N&'),"0#),C'P
The master has to
handle only one
Master TCP connection.

Relay
Slave
log_slave_updates

Slave Slave Slave Slave Slave

R/?0/.:0*/-3.?2+*/<AAA
-7'0G),+F7.)'05-.3,<'0'/<*/'

Master

engine = blackhole The relay slave

Relay
manages replication
Slave
logs, but not actual
data.

Slave Slave Slave Slave Slave

&'()*+,-*./0
4.;;,/?5
A quick run-through of the commands
#9B60!R#1K&0#1R1S#
! Used on master
! Requires SUPER or REPLICATION CLIENT privileges
! Gives log file and position master is writing to
! Also shows database filters used

mysql> SHOW MASTER STATUS;

+---------------+----------+--------------+------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+---------------+----------+--------------+------------------+
| mysql-bin.003 | 73 | test | manual,mysql |
+---------------+----------+--------------+------------------+
#9B60TUVR&W0%BH#
! Used on master
! Requires SUPER privileges
! Will display a list of binary logs on the server
! Use it before using PURGE BINARY LOGS

mysql> SHOW BINARY LOGS;

+---------------+-----------+
| Log_name | File_size |
+---------------+-----------+
| binlog.000015 | 724935 |
| binlog.000016 | 733481 |
+---------------+-----------+
#9B60TUV%BH0KXKV1#
! Used on master
! Requires REPLICATION SLAVE privileges
! Show events in binary log
! Also check mysqlbinlog utility
mysql> SHOW BINLOG EVENTS FROM 390 LIMIT 1\G
*************************** 1. row ***************************
Log_name: slave-bin.000001
Pos: 390
Event_type: Query
Server_id: 2
End_log_pos: 476
Info: use `test`; create table t1 (a int)
1 row in set (0.00 sec)
#9B60#%RXK09B#1#
! Used on master
! Requires REPLICATION SLAVE privileges
! Shows list of slaves currently registered with the master
! Only slaves started with report-host option are visible

mysql> SHOW SLAVE HOSTS;

+-----------+-----------+------+-----------+
| Server_id | Host | Port | Master_id |
+-----------+-----------+------+-----------+
| 2 | 127.0.0.1 | 9308 | 1 |
+-----------+-----------+------+-----------+
1 row in set (0.00 sec)
QS&HK0TUVR&W0%BH#
! Used on master
! Requires SUPER privileges
! Removes log files before a certain log file or date
! MASTER can be used in place of BINARY
! Alternative is to use variable EXPIRE_LOGS_DAYS
#K10#$%O%BHOTUV
! Used on master
! Requires SUPER privileges
! Session variable
! Controls logging to binary log
! Does not work for NDB!

mysql> SET SQL_LOG_BIN=0;

mysql> INSERT INTO t1 VALUES (1,2,3);
mysql> SET SQL_LOG_BIN=1;
#K10H%BTR%0KYQU&KO%BH#OZRW#
! Used on master
! Require SUPER privileges
! 0 means ”never expire”
! Positive value means expire logs after this many days
! Logs will be removed at startup or binary log rotation
! Can be used with running slave
! Logs are removed! Make sure you have backup!
&K#K10!R#1K&
! Used on master
! Requires RELOAD privileges
! Deletes all binary logs in the index file!
! Resets binary log index
! Used to get a ”clean start”
! Use with caution! You lose data!
#9B60#%RXK0#1R1S#
! Used on slave
! Requires SUPER or REPLICATION CLIENT privileges
! Shows some interesting information:
If the slave threads are running
What position the I/O thread read last
What position the SQL thread executed last
Error message and code, if thread stopped due to an error
#9B60#%RXK0#1R1S#0[\AD]
! mysql> SHOW SLAVE STATUS\G
****************** 1. row ******************
Slave_IO_State: Last_Errno: 0
Master_Host: 127.0.0.1 Last_Error:
Master_User: root Skip_Counter: 0
Master_Port: 10190 Exec_Master_Log_Pos: 0
Connect_Retry: 1 Relay_Log_Space: 102
Master_Log_File: Until_Condition: None
Read_Master_Log_Pos: 4 Until_Log_File:
Relay_Log_File: slave-relay-bin.000001 Until_Log_Pos: 0
Relay_Log_Pos: 4 Master_SSL_Allowed: No
Relay_Master_Log_File: Master_SSL_CA_File:
Slave_IO_Running: No Master_SSL_CA_Path:
Slave_SQL_Running: No Master_SSL_Cert:
Replicate_Do_DB: Master_SSL_Cipher:
Replicate_Ignore_DB: Master_SSL_Key:
Replicate_Do_Table: Seconds_Behind_Master: NULL
Replicate_Ignore_Table: Last_IO_Errno: 0
Replicate_Wild_Do_Table: Last_IO_Error:
Replicate_Wild_Ignore_Table: Last_SQL_Errno: 0
Last_SQL_Error:
1 row in set (0.00 sec)
49RVHK0!R#1K&01B
! Used on slave
! Requires SUPER privileges
! Configures the slave server connection to the master
! Slave should not be running
! The user need REPLICATION SLAVE privileges on master

CHANGE MASTER TO
MASTER_HOST=’adventure.com’,
MASTER_USER=’dragon’,
MASTER_PASSWORD=’xyzzy’;
#1R&10#%RXK0,/?0#1BQ0#%RXK
! Used on slave
! Used to start or stop the slave threads
! Defaults to affecting both I/O and SQL thread
! ... but individual threads can be started or stopped
START SLAVE SQL_THREAD
START SLAVE IO_THREAD
&K#K10#%RXK
! Used on slave
! Removes all info on replication position
Deletes master.info, relay-log.info and all relay logs
! Relay logs are unconditionally removed!
... even if they have not been fully applied
#K10H%BTR%0#$%O#%RXKO#^UQO4BSV1K&
! Used on slave
! Global server variable
! Requires SUPER privileges
! Slave SQL thread shall not be running
! Slave will skip events when starting
! Useful when recovering from slave stops
! Might leave master and slave with different data in tables
... so be careful when you use it
S5'04,5'5
S5'04,5'5M0Q,3-0D0@ T,5*+0&'()*+,-*./
Intensive Reads High Availability
Master

Master/ Master/
Slave Slave

Slave
Slave

Slave
N#('+*,)*5-P05),C'50@ G,+F2(50,/?03'(.3-*/<

Master

Slave
Slave
Slave reports
Slave
Slave
backups
 N#('+*,)*5-P05),C'50@ ('3_,(()*+,-*./

friends: 10 GB
Master
messages: 30
GB

Slave Slave
Slave
Slave

“friends list” queries “message board” queries

 N#('+*,)*5-P05),C'50@ T),+F7.)'0K/<*/'

Master

Slave
Slave
Slave
Slave “message board” queries
(friends table in black
“friends list” queries
hole)
(message table in black
hole)
17*/<50-.0-7*/F0,G.2-0*/0G,5*+03'()*+,-*./

! Initial snapshot of slaves

! load balancing of clients
! Failover of clients to new master
9R0`0#+,)'0.2-8

Master/ Master/
Slave Slave

Slave
Slave

Slave
R/"0G'--'38
Master/ Master/
Slave Slave

Proxy
Master

Slave
Slave

Slave
Q3.G)';E05),C'0=,*).C'30-.0,0/':0;,5-'3
! Look at SHOW SLAVE STATUS. This gives the file and
position on the failed master.
! “File 34 position 6000” on the failed master may correspond
to “File 33 position 22000” on the new master. Find the
corresponding file and position.
! CHANGE MASTER TO
master_host = ...
master_log_file = ...
master_log_pos = ...
! START SLAVE
9,/?)*/<0-7'0=,*).C'30(3.G)';
1. Automate it (scripting)
2. Avoid it
S5'04,5'5M0Q,3-0I0@ 9R0,/?0#+,)'0B2-

Architecture 1: Pair of masters –

Active & Standby
Virtual IP address
Heartbeat Manager Slave

Master Master
Slave
Shared Disk Array
 S5'04,5'5M0Q,3-0I0@ 9R0,/?0#+,)'0B2-
2: MySQL Cluster as master, MySQL slaves

Cluster Cluster

Slave Slave
Slave
S5'04,5'5M0Q,3-0I0@ 9R0,/?0#+,)'0B2-
Virtual IP address

Master Master

Virtual IP address Shared

Disk Array
Virtual IP address
Proxy Proxy
Master Master

3: Master and
Slave Slave proxy master are
Slave both HA pairs
 S5'04,5'5M0Q,3-0I0@ 9R0,/?0#+,)'0B2-
4: Replicate from
NDB Cluster Cluster
Cluster through
HA proxy pair
Virtual IP address

Blackhole Proxy Proxy

Master Master

Shared Disk Array

InnoDB Slave Slave

Slave
 R(()*+,-*./_)'C')0(,3-*-*./*/<0,/?0-7'0a'?'3,-'?0
K/<*/'
Friends
Master How to JOIN friends table with
message table? Message
Master

Slave
Slave
Slave
Slave
“friends list” slaves
“message board” slaves
 R(()*+,-*./_)'C')0(,3-*-*./*/<0,/?0-7'0a'?'3,-'?0
K/<*/'
Friends
Master

Message
Master
“friends list”
Slave
Slave slaves
CREATE TABLE messages (
id int unsigned ...
) ENGINE=FEDERATED
CONNECTION=”mysql://feduser:fedpass@message-master/
friendschema/messages”;
S5'04,5'5M0Q,3-0L0@ !2)-*()'0Z,-,04'/-'35
secure
)*+$,&-"$ tunnel !"#$%&'(
rep
Active
Master
Master
wr wr

wr wr
Slave Slave
rd rd
app app

Slave Slave

( Jeremy Cole – MySQL Users Conf 2006 )

 R=-'30a,*).C'3
secure
)*+$,&-"$ tunnel !"#$%&'(
rep
Active
Master
Master
wr wr

wr wr
Slave Slave
rd app app rd

Slave Slave

( Jeremy Cole – MySQL Users Conf 2006 )

&.:_G,5'?0
3'()*+,-*./
&.:_G,5'?03'()*+,-*./0[!"#$% \AD]

! Statement-based replication
Replicate statement doing changes
Requires up-to-date slave
Requires determinism
! Row-based replication
Replicate actual row changes
Does not require up-to-date slave
Can handle any statement
4.;(,3*5./0.=03'()*+,-*./0;'-7.?5

! Row-based replication
Can handle ”difficult” statements
Required by cluster
! Statement-based replication
Sometimes smaller binary log
Binary log can be used for auditing
&.:_G,5'?03'()*+,-*./0=',-23'5

! Log is idempotent
... provided all tables in log have primary key

! Statement events and row events can be mixed in log

... so format can be switched during run-time
(slave switches automatically as required)
... and even different formats for different threads
&.:_G,5'?03'()*+,-*./0,50,0=.2/?,-*./

! Conflict detection and conflict resolution

! Fine-grained filtering
! NDB Cluster replication
! Multi-channel replication
! Horizontal partitioning
... sending different rows to different slaves
a*)-'3*/<
! For statement-based replication:
Statements are filtered
Filtering is based on current (used) database
Master filtering are on database only
! For row-based replication:
Rows are filtered
Filtering is based on actual database and table
Master filtering for individual tables possible
... but not implemented
6,/-0G.-705-,-';'/-0,/?03.:0=.3;,-8

Master Slave

STMT ROW

! Master in STATEMENT mode, slave in ROW mode

! Slave converts statements executed into row format
! Once in row format, it stays in row format
T*/,3"0%.<
Modes and Formats of the Binary Log
%.<<*/<0;.?'5

! Three modes: STATEMENT, MIXED, and ROW

! Server variable BINLOG_FORMAT controls mode
! Mode is used to decide logging format for statements
Logging format is representation of changes
More about that in just a bit
#K10TUV%BHO!BZK
! SET BINLOG_FORMAT=mode

! Session and global variable

! Mode is one of STATEMENT, ROW, or MIXED
! STATEMENT: statements are logged in statement format
! ROW: statements are logged in row format
! MIXED (default)
Statements are logged in statement format by default
Statements are logged in row format in some cases
#:*-+7*/<0;.?'5
! Mode can be switched at run-time
... even inside a transaction
! Switching mode is not allowed:
If session has open temporary tables
From inside stored functions or triggers
If ‘ndb’ is enabled
!UYKZ0;.?'
! Safe statements are usually logged in statement format
! Unsafe statements are logged in row format
! Heuristic decision on what is unsafe, currently:
Statement containing UUID() or calls to UDFs

Statements updating >1 table with auto-increment columns

INSERT DELAYED statements
problems with RAND() and user-defined variables
T*/,3"0).<<*/<0=.3;,-5
! The format tells how changes are stored in log
! Two formats: statement and row
! Formats can be mixed in binary log

mysql> show binlog events;

+----------+-----+-------------+---+----------------------------------------+
| Log_name | Pos | Event_type | … | Info |
+----------+-----+-------------+---+----------------------------------------+
| ... | 4 | Format_desc | … | Server ver: 5.1.17-beta-debug-log... |
| ... | 105 | Query | … | use `test`; CREATE TABLE tbl (a INT) |
| ... | 199 | Query | … | use `test`; INSERT INTO tbl VALUES (1) |
| ... | 290 | Table_map | … | table_id: 16 (test.tbl) |
| ... | 331 | Write_rows | … | table_id: 16 flags: STMT_END_F |
+----------+-----+-------------+---+----------------------------------------+
5 rows in set (0.00 sec)
#-,-';'/-0).<<*/<0=.3;,-
! The statement executed is logged to the binary log
! Statement logged after statement has been executed
! Pro:
Usually smaller binary logs
Binary log can be used for auditing
! Cons:
Cannot handle partially executed statements
Cannot handle non-deterministic data
Does not work with all engines (e.g., NDB)
&.:0).<<*/<0=.3;,-
! The actual rows being changed are logged
! Rows are grouped into events
! Pro:
Can handle non-deterministic statements
Can handle UDF execution
Idempotent
! Cons:
No easy way to see what rows are logged
Does not work with all engines (e.g., blackhole)
Kb,;()'E0;2)-*_-,G)'02(?,-'

! UPDATE t1,t2 SET t1.b = ..., t2.b = ...

mysql> show binlog events from 480;

+----------+-----+-------------+---+----------------------------------------+
| Log_name | Pos | Event_type | … | Info |
+----------+-----+-------------+---+----------------------------------------+
| ... | 480 | Table_map | … | table_id: 16 (test.t1) |
| ... | 520 | Table_map | … | table_id: 17 (test.t2) |
| ... | 560 | Update_rows | … | table_id: 16 |
| ... | 625 | Update_rows | … | table_id: 17 flags: STMT_END_F |
+----------+-----+-------------+---+----------------------------------------+
4 rows in set (0.00 sec)
 Kb,;()'E04&KR1K_#K%K41

! CREATE t3 SELECT * FROM t1

mysql> show binlog events from 690;

+----------+-----+-------------+---+----------------------------------------+
| Log_name | Pos | Event_type | … | Info |
+----------+-----+-------------+---+----------------------------------------+
| ... | 480 | Table_map | … | use `test`; CREATE TABLE `t3` (
a INT(11) DEFAULT NULL,
b INT(11) DEFAULT NULL
) |
| ... | 520 | Table_map | … | table_id: 18 (test.t3) |
| ... | 625 | Write_rows | … | table_id: 18 flags: STMT_END_F |
+----------+-----+-------------+---+----------------------------------------+
3 rows in set (0.00 sec)
#('+*,)0+,5'5
! TRUNCATE vs. DELETE in row mode
TRUNCATE is logged in statement format
DELETE is logged in row format
! GRANT, REVOKE, and SET PASSWORD
These statements changes rows in mysql tables:
tables_priv, columns_priv, and user
Replicated in statement format
Other statements on these tables are replicated in row format
9.:0.Gc'+-50,3'0).<<'?

! Databases ! Stored functions

! Tables ! Triggers
! Views ! Events
! Stored procedures ! Users

We are here only considering how these objects are logged

when using row mode
For statement mode, everything is logged in statement format
Z,-,G,5'50,/?01,G)'5

! Database manipulation statements

Logged in statement format
! Table manipulation statements
Statement format: CREATE, ALTER, and DROP
Row format: INSERT, DELETE, UPDATE, etc.
X*':5
! CREATE, ALTER, and DROP logged in statement format
! Changes are logged by logging changes to the tables

mysql> UPDATE living_in SET name='Matz' WHERE name=’Mats’;

Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0

mysql> show binlog events from 1605;

+----------+------+-------------+-----+--------------------------------+
| Log_name | Pos | Event_type | ... | Info |
+----------+------+-------------+-----+--------------------------------+
| maste... | 1605 | Table_map | ... | table_id: 17 (test.names) |
| maste... | 1648 | Update_rows | ... | table_id: 17 flags: STMT_END_F |
+----------+------+-------------+-----+--------------------------------+
2 rows in set (0.01 sec)
#-.3'?0(3.+'?23'5
! CREATE, ALTER, and DROP are replicated in statement
format (with a DEFINER)
! CALL is logged in row format by logging all changes done by
the call
mysql> create procedure foo(a int) insert into t1 values(a);
mysql> show binlog events from 102\G
*************************** 1. row ***************************
Log_name: master-bin.000001
Pos: 102
Event_type: Query
Server_id: 1
End_log_pos: 244
Info: use `test`; CREATE DEFINER=`root`@`localhost` procedure foo(a
int) insert into t1 values(a)
1 row in set (0.00 sec)
#-.3'?0=2/+-*./5
! CREATE, ALTER, and DROP are replicated in statement
format (with a DEFINER)
! The effects of calling a stored function are logged in row
format

mysql> select a, bar(a) from t2;

mysql> show binlog events from 557;
+----------+-----+------------+-----+--------------------------------+
| Log_name | Pos | Event_type | ... | Info |
+----------+-----+------------+-----+--------------------------------+
| maste... | 557 | Table_map | ... | table_id: 18 (test.t1) |
| maste... | 596 | Write_rows | ... | table_id: 18 flags: STMT_END_F |
+----------+-----+------------+-----+--------------------------------+
2 rows in set (0.01 sec)
13*<<'35
! CREATE, ALTER, and DROP are replicated in statement
format (with a DEFINER)
! The effects of a trigger are logged in row format

mysql> insert into t1 values (1,2);

mysql> show binlog events from 780;
+----------+-----+-------------+---+----------------------------------------+
| Log_name | Pos | Event_type | … | Info |
+----------+-----+-------------+---+----------------------------------------+
| ... | 780 | Table_map | … | table_id: 16 (test.t1) |
| ... | 820 | Table_map | … | table_id: 17 (test.t2) |
| ... | 860 | Write_rows | … | table_id: 16 |
| ... | 925 | Write_rows | … | table_id: 17 flags: STMT_END_F |
+----------+-----+-------------+---+----------------------------------------+
4 rows in set (0.00 sec)
KC'/-5
! CREATE, ALTER, and DROP are replicated in statement
format (with a DEFINER)
! The event is disabled on the slave
! Effects of a event are logged in row format
U;()';'/-,-*./
How replication works
 !"#$%0&'()*+,-*./0R3+7*-'+-23'
!"#$%0dAe_\Ae

Application Application Application Application

Parse/optimize/execute Statements
flushed at
MySQL Server commit MySQL Server
SBR !,5-'3 #),C'
&'()*+,-*./ I/O
thread SQL
thread

Rows
SE1 SE2 SE1 SE2
Relay
Binlog Binlog
Storage Binlog
engine
interface Storage Engines Storage Engines
 !"#$%0&'()*+,-*./0R3+7*-'+-23'
!"#$%0\ADE0&.:_G,5'?03'()*+,-*./0[&T&]
Application Application Application Application

Parse/optimize

MySQL Server MySQL Server

SBR !,5-'3 #),C'
&'()*+,-*./ I/O
thread SQL
thread
RBR

SE1 SE2 SE1 SE2

Relay
Binlog Binlog
Binlog

Storage Engines Storage Engines

 &.:_G,5'?0&'()*+,-*./
4.;(,3*5*./0G'-:''/0#T&0,/?0&T&

Advantages of Row-based Replication (RBR)

• Can replicate non-deterministic statements (e.g. UDFs, LOAD_FILE(),
UUID(), USER(), FOUND_ROWS())
• Makes it possible to replicate between MySQL Clusters (having multiple
MySQL servers or using NDB API)
• Less execution time on slave
• Simple conflict detection (that is currently being extended)

Advantages of Statement-based Replication (SBR)

• Proven technology (since MySQL 3.23)
• Sometimes produces smaller log files
• Binary log can be used for auditing
 a.230/':0G*/).<0'C'/-5
1.Table map event
–Semantics: “This table id matches this table definition”
2.Write event (After image)
–Semantics: “This row shall exist in slave database”
3.Update event (Before image, After image)
–Semantics: “This row shall be changed in slave database”
4.Delete event (Before image)
–Semantics: “This row shall not exist in the slave database”

Various optimizations:
•Only primary key in before image. Works if table has PK
•Only changed column values in after image. Works if table has PK

Log is idempotent if PK exists and there are only RBR events in log.
Slave can execute both SBR and RBR events.
4)25-'3
&'()*+,-*./
 !"#$%04)25-'30&'()*+,-*./
%.+,)0,/?0H).G,)0&'?2/?,/+"
Application Application Application Application Application Application

Replication
MySQL MySQL MySQL MySQL MySQL MySQL
Server Server Server Server Server Server

ZT ZT ZT ZT

ZT ZT ZT ZT

H).G,)
%.+,)0#"/+73./.250 R5"/+73./.25
&'()*+,-*./0@ &'()*+,-*./
-:._(7,5'0+.;;*-
1..)5
,/?
1'+7/*>2'5
!,F*/<0,05/,(57.-0=3.;0,0;,5-'30?,-,G,5'

! This is necessary for bringing new slaves online.

! Options:
Shut down master & take offline backup
Use “ibbackup” to make an online physical backup
www.innodb.com

Use mysqldump --master-data

1,G)'047'+F52;5
! How do you know the slave really has the same data as the
master?
! Guiseppe Maxia
Taming the Distributed Data Problem – MySQL Users Conf
2003
! Baron Schwartz
MySQL Table Checksum
http://sourceforge.net/projects/mysqltoolkit
 NZ'),"'?0&'()*+,-*./P
! Bruce Dembecki, LiveWorld
Lessons from an Interactive Environment – MySQL Users
Conf 2005
! Provides hourly log snapshots and protection against “user
error” (e.g. DELETE FROM important_table)

Time 3:10 4:00 4:01 4:05 4:10

I/O
Flush
2:05 to 3:05 logs 3:05 to 4:05
SQL
!,/,<*/<0X*3-2,)0UQ0,??3'55'5

! Fof failover and high availability. (Always prefer virtual IP

addresses rather than DNS changes)
! Heartbeat – www.linux-ha.org
also runs on Solaris, BSD, Mac OS X
! Several other software alternatives
Sun Cluster, HP ServiceGuard, etc.
! Or a hardware load balancer
F5 Big IP, Foundry ServerIron, etc.
#7,3'?0#-.3,<'0=.30R+-*C'f#-,/?G"0(,*35
! DRBD
www.drbd.org
! Hardware SAN
! Hardware NAS
NetApp
12//')50g0(3.b*'50-.025'0=.30;,/,<*/<0;2)-*()'0
?,-,0+'/-'35

! Master & slaves can use SSL

! ... or offload the SSL processing to other servers using
stunnel
www.stunnel.org
! Proxy writes to masters as in Jeremy Cole’s example
TCP Proxy software
Hardware load balancer
 &'='3'/+'5
• MySQL Manual (http://dev.mysql.com/doc/)
Chapter: Replication
• MySQL Manual (http://dev.mysql.com/doc/)
Chapter: MySQL Cluster Replication
• MySQL Forums (http://forums.mysql.com/)
MySQL Replication forum

• Replication Tricks and Tips

Tuesday 4:25pm
• BOF: Replication
Tuesday evening, first slot (probably 7:30pm)

lars@mysql.com, mats@mysql.com
www.mysql.com
 4.;;./0KC'/-09',?'30@ Dh0G"-'5
Field Length Description
Timestamp 4 bytes Seconds since 1970
Type 1 byte Event type
Master Id 4 bytes Server Id of server that created this event

Total size 4 bytes Event total size in bytes

Master position 4 bytes Position of next event in master binary log
Flags 2 bytes Flags for event

time stamp type master id

total size master position flags

#-,-';'/-_G,5'?0UV#K&10DfIE0$2'3"0'C'/-07',?'3

$ mysqlbinlog --hexdump master-bin.000001

# at 235
#060420 20:16:02 server id 1 end_log_pos 351
# Position Timestamp Type Master ID
# 000000eb e2 cf 47 44 02 01 00 00 00
# Size Master Pos Flags
# 74 00 00 00 5f 01 00 00 10 00
#-,-';'/-_G,5'?0UV#K&10IfIE0$2'3"0'C'/-0?,-,

$ mysqlbinlog --hexdump master-bin.000001

# 000000fe 02 00 00 00 00 00 00 00
# 04 00 00 1a 00 00 00 40 |................|
# 0000010e 00 00 ... |.............std|
# 0000011e 04 08 ... |.......test.INSE|
# 0000012e 52 54 ... |RT.INTO.t1.VALUE|
# 0000013e 53 20 ... |S...A...B......X|
# 0000014e 27 2c ... |...Y......X...X.|
# 0000015e 29 |.|
# Query thread_id=2 exec_time=0 error_code=0

SET TIMESTAMP=1145556962;
INSERT INTO t1 VALUES ('A','B'), ('X','Y'), ('X','X');
 &.:_G,5'?0UV#K&10DfIE01,G)'0;,(0'C'/-

$ mysqlbinlog --hexdump master-bin.000001

# at 235
#060420 20:07:01 server id 1 end_log_pos 275
# Position Timestamp Type Master ID
# 000000eb c5 cd 47 44 13 01 00 00 00
# Size Master Pos Flags
# 28 00 00 00 13 01 00 00 00 00
# 000000fe 0f 00 00 00 00 00 00 00
04 74 65 73 74 00 02 74 |.........test..t|
# 0000010e 31 00 02 fe fe |1....|
# Table_map: `test`.`t1` mapped to number 15
BINLOG 'xc1HRBMBAAAAKAAAABMBA...3QAAnQxAAL+/g==';
 &.:_G,5'?0UV#K&10IfIE063*-'0'C'/-

$ mysqlbinlog --hexdump master-bin.000001

# at 275
#060420 20:07:01 server id 1 end_log_pos 319
# Position Timestamp Type Master ID
# 00000113 c5 cd 47 44 14 01 00 00 00
# Size Master Pos Flags
# 2c 00 00 00 3f 01 00 00 10 00
# 00000126 0f 00 00 00 00 00 01 00
# 02 ff f9 01 41 01 42 f9 |............A.B.|
# 00000136 01 58 01 59 f9 01 58 01
# 58 |.X.Y..X.X|
# Write_rows: table id 15

BINLOG 'xc1HRBQBAAAALAAAAD...EBQvkBWAFZ+QFYAVg=';
 !"#$%04)25-'30&'()*+,-*./
67'3'0-.0<'-0-7'0).<0'C'/-580

Application Application Application

Replication
MySQL MySQL MySQL
Server Server Server

Application
ZT ZT

Application ZT ZT

Application MySQL Cluster

using NDB API
 !"#$%04)25-'30&'()*+,-*./
4./+233'/+"0+./-3.)0*/5*?'0;,5-'30+)25-'3
Application Application

MySQL MySQL
Server Server

TC (DB y) TC (DB x)

DB 1 DB 3
Row-level
locking
on primary
replica DB 2 DB 4

Node group 1 Node group 2

 !"#$%04)25-'30&'()*+,-*./
%.<057*((*/<0*/5*?'0;,5-'30+)25-'3
Application Application
Changed Replication
row data
MySQL MySQL MySQL
Server Server Server

TC (DB x) TC (DB x)
Replication
server

DB 1 DB 3

Row-level
locking
on primary DB 2 DB 4
replica
Node group 1 Node group 2
 !"#$%0&'()*+,-*./0R3+7*-'+-23'
!"#$%0\AD

Application Application Application Application

MySQL Server MySQL Server

!,5-'3 #),C'
SBR &'()*+,-*./ &'()*+,-*./
5'3C'3 I/O
SQL
thread
RBR thread

Injector
interface SE1 SE2 SE1 SE2
Relay
Binlog Binlog
NDB Binlog
Injector
Storage Engines
Storage Engines
Row-based log from
cluster data nodes
 !"#$%04)25-'30&'()*+,-*./
T'7,C'50)*F'0.3?*/,3"0!"#$%0&'()*+,-*./
Application Application Application Application Application Application

Replication
MySQL MySQL MySQL MySQL MySQL MySQL
Server Server Server Server Server Server

ZT ZT ZT ZT

ZT ZT ZT ZT

H).G,)
%.+,)0#"/+73./.250 R5"/+73./.25
&'()*+,-*./0@ &'()*+,-*./
-:._(7,5'0+.;;*-