Mysql PN Replication Gtid Failover

MySQL 5.
6 Replication:
Self-Healing Clusters with GTIDs
Safe Harbour Statement

The following is intended to outline our general product direction. It is
intended for information purposes only, and may not be incorporated into any
contract.
It is not a commitment to deliver any material, code, or functionality, and
should not be relied upon in making purchasing decisions. The development,
release, and timing of any features or functionality described for Oracles
products remains at the sole discretion of Oracle.
`2
Copyright 2012, Oracle and/or its affiliates. All rights reserved. |
PART 1
Fail-over Base
Global Transaction Identifiers
Overview
Automatic Positioning
Hands-On
PART 2
Under the Hood Become a GTID Expert
How Slave Preserves GTIDs
GTIDs Must Be Unique
Integration With Other Features

Seeking & Skipping: Empty Transactions
Purging Binary Logs
Provisioning a Slave From a Backup
`3
Introduction to MySQL Replication ! Fail-over Base ! Under the Hood ! Integration With Other Features
Fail-over
Crash can happen to anyone:

Hardware failure
Human mistake
Bug
Natural disaster
Automatic fail-over with Global Transaction Identifiers:

Reduces admin overhead
Prevents planned downtime
Prevents unplanned downtime
`4
Fail-over
Handle server crash with minimal disruption

Example 1: tree
B
A
C
`5
Fail-over

Example 1: tree
B
A
Crash
C
`6
Fail-over

Example 1: tree
B
A
C
`7
Fail-over

Example 1: tree
Make B the new master
A
C
`8
Fail-over

Example 1: tree
Example 2: line
`9
Fail-over

Example 1: tree
Example 2: line
`10
B
Crash
Fail-over

Example 1: tree
Example 2: line
`11
Fail-over

Example 1: tree
Make A direct master of C
Example 2: line
`12
Fail-over

Example 1: tree
Example 2: line
Example 3: circle
`13
Fail-over

Example 1: tree
Example 2: line
D
Crash
Example 3: circle
`14
Fail-over

Example 1: tree
Example 2: line
Example 3: circle
`15
Fail-over

Example 1: tree
Example 2: line
Example 3: circle
Make a shortcut
in the circle
`16
Fail-over

Example 1: tree
Example 2: line
Example 3: circle
Example 4: scheduled maintenance
`17
Fail-over
Take
out D!
Example 1: tree
Example 2: line
Example 3: circle
`18
Fail-over

Example 1: tree
Example 2: line
Maintain
D offline,
without
disrupting
service
Example 3: circle
`19
Fail-over

Example 1: tree
Example 2: line
Example 3: circle
`20
Fail-over

Example 1: tree
Example 2: line
Example 3: circle
Example 5: arbitrary topology
`21
D
C
E
F
Wow!
I really want to get started
with fail-over. Tell me more!
`22
Introduction to MySQL Replication
Overview
Fail-over Base
Hands-On


Purging Binary Logs
`23
Server assigns Global Transaction Identifier (GTID) to every
transaction:
server_uuid:number
a61678ba-4889-4279-9e58-45ba840af334:1
server_uuid identifies the server; globally unique
number is incremented by 1 for each transaction on this server
`24
transaction:
server_uuid:number
a61678ba-4889-4279-9e58-45ba840af334:1
Writes GTID to binary log
`25
transaction:
server_uuid:number
a61678ba-4889-4279-9e58-45ba840af334:1
Writes GTID to binary log

Slave ensures transaction gets the same GTID when re-executed
`26

master> CREATE TABLE t1 (a INT);
master> SELECT @@global.gtid_executed;
a61678ba-4889-4279-9e58-45ba840af334:1
New variable:
gtid_executed
master> INSERT INTO t1 VALUES (1);

master> INSERT INTO t1 VALUES (2);
a61678ba-4889-4279-9e58-45ba840af334:1-3
`27
Note: interval

a61678ba-4889-4279-9e58-45ba840af334:1-10000
slave> SELECT @@global.gtid_executed;
a61678ba-4889-4279-9e58-45ba840af334:1-9999
`28

a61678ba-4889-4279-9e58-45ba840af334:1-10000
slave> SELECT @@global.gtid_executed;
a61678ba-4889-4279-9e58-45ba840af334:1-9999
Slave is missing
one transaction
`29
OK, I get it.

So we have GTIDs.
How are they used in fail-over?
`30
Overview
Fail-over Base
Hands-On


Purging Binary Logs
`31
`32
Example 1: tree
B
A
id1,trx1,
id2,trx2,
id3,trx3
(crashed)
(master)
id1,trx1,
id2,trx2
(slave)
id1,trx1
C
(slave)
`33
Example 1: tree
B
id1,trx1,
id2,trx2,
ACrash!
id3,trx3
(crashed)
(master)
id1,trx1,
id2,trx2
(slave)
id1,trx1
C
(slave)
`34
Example 1: tree
What the
slave has
B
A
id1,trx1,
id2,trx2,
id3,trx3
(crashed)
(crashed)
`35
id1,trx1,
id2,trx2
id1
(slave)
id2, trx2,...
What the
slave does
not have
id1,trx1
C
(slave)
Example 1: tree
Example 2: circle
`36
client
client
Example 1: tree
Example 2: circle
client
client trx1
id1,trx1
`37
Example 1: tree
Example 2: circle
client trx2
client trx1
id2,trx2
`38
id1,trx1,
id2,trx2
Example 1: tree
Example 2: circle
client trx2
client trx1, trx3
id2,trx2
`39
id1,trx1,
id2,trx2,
id3,trx3
Example 1: tree
Example 2: circle
client trx2
client trx1, trx3
id2,trx2
`40
id1,trx1,
id2,trx2,
id3,trx3
C Crash!
Example 1: tree
Example 2: circle
client trx2
client trx1, trx3
id2,trx2
What the
slave has
`41
B
id2
id1,trx1,id3,trx3,...
id1,trx1,
id2,trx2,
id3,trx3
What the
slave does
not have
Awesome!
I'm really eager to get started.
How do I set it up?
`42
Overview
Fail-over Base
Hands-On


Purging Binary Logs
`43
Hands-On
Prerequisites:
Use transactional storage engine for all tables (InnoDB)
Don't use CREATE TABLE SELECT
Don't execute CREATE TEMPORARY TABLE or
DROP TEMPORARY TABLE inside a transaction
`44
Hands-On
Prepare the server for fail-over
1.Sync and stop all servers

2.Add to every my.cnf:
gtid-mode=on
enforce-gtid-consistency=on
log-bin
log-slave-updates
3.Start all servers
4.Execute:
> CHANGE MASTER TO MASTER_AUTO_POSITION = 1
`45
Hands-On
Perform fail-over
On the slave, simply point to the new master:

> CHANGE MASTER TO MASTER_HOST = '<host>',
MASTER_PORT = <port number>,
MASTER_USER = '<user name>'
MASTER_PASSWORD = 'secret';
No positions needed!
`46
Hands-On
Perform fail-over
B
A
C
`47
CHANGE MASTER TO
MASTER_HOST = 'B',
MASTER_PORT = <B's port>,
Hands-On
Perform fail-over
`48
CHANGE MASTER TO
MASTER_HOST = 'A',
MASTER_PORT = <A's port>,
More on GTIDs
Next
Steps
svenmysql.blogspot.co.uk
More on MySQL 5.6 Replication

http://dev.mysql.com/tech-resources/articles/
mysql-5.6-replication.html
Try Out MySQL 5.6RC

http://dev.mysql.com/downloads/mysql/
`49

Mysql PN Replication Gtid Failover

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mysql PN Replication Gtid Failover

Uploaded by

Copyright:

Available Formats

MySQL 5.

Safe Harbour Statement

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Integration With Other Features

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Crash can happen to anyone:

Automatic fail-over with Global Transaction Identifiers:

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Make B the new master

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Make A direct master of C

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Handle server crash with minimal disruption

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Introduction to MySQL Replication

Under the Hood Become a GTID Expert

Integration With Other Features

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Global Transaction Identifiers

Server assigns Global Transaction Identifier (GTID) to every

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Global Transaction Identifiers

Server assigns Global Transaction Identifier (GTID) to every

Writes GTID to binary log

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Global Transaction Identifiers

Server assigns Global Transaction Identifier (GTID) to every

Writes GTID to binary log

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |

Global Transaction Identifiers

master> INSERT INTO t1 VALUES (1);

Copyright 2012, Oracle and/or its affiliates. All rights reserved. |