Home |  MySQL Buzz |  FAQ |  Feeds |  Submit your blog feed |  Feedback |  Archive |  Aggregate feed RSS 2.0 English Deutsch Español Français Italiano 日本語 Русский Português 中文
Showing entries 1 to 4

Displaying posts with tag: gtids (reset)

How to use MySQL Global Transaction IDs (GTIDs) in production
+1 Vote Up -0Vote Down

Reconfiguring replication has always been a challenge with MySQL. Each time the replication topology has to be changed, the process is tedious and error-prone because finding the correct binlog position is not straightforward at all. Global Transaction IDs (GTIDs) introduced in MySQL 5.6 aim at solving this annoying issue.

The idea is quite simple: each transaction is associated with a unique identifier shared by all servers in a given replication topology. Now reconfiguring replication is easy as the correct binlog position can be automatically calculated by the server.

Awesome? Yes it is! However GTIDs are also changing a lot of things in how we can perform operations on replication. For instance,

  [Read more...]
How to use MySQL Global Transaction IDs (GTIDs) in production
+0 Vote Up -0Vote Down

Reconfiguring replication has always been a challenge with MySQL. Each time the replication topology has to be changed, the process is tedious and error-prone because finding the correct binlog position is not straightforward at all. Global Transaction IDs (GTIDs) introduced in MySQL 5.6 aim at solving this annoying issue.

The idea is quite simple: each transaction is associated with a unique identifier shared by all servers in a given replication topology. Now reconfiguring replication is easy as the correct binlog position can be automatically calculated by the server.

Awesome? Yes it is! However GTIDs are also changing a lot of things in how we can perform operations on replication. For instance, skipping

  [Read more...]
Enabling MySQL Multi-Source Replication Workflows with GTIDs
Employee +6 Vote Up -0Vote Down
The goal of this post is twofold: (i) to show the power of GTIDs and MySQL 5.6 replication infrastructure in general; and (ii) show MySQL users a way to hack multi-source replication rather painlessly and rather quickly on top of MySQL 5.6 when using the new MySQL 5.6 replication features.

Multi-source Replication

Multi-source replication is often regarded as a mean to aggregate, consolidate, different streams of data into one single server instance, a sink. In many cases the following assumptions hold:
  • There are no conflicts between transactions from different sources/masters;
  • Replication is asynchronous
  •   [Read more...]
    MySQL Replication: Self-Healing Recovery with GTIDs and MySQL Utilities
    Employee_Team +2 Vote Up -0Vote Down

    MySQL 5.6 includes a host of enhancements to replication (http://www.mysql.com/products/enterprise/replication.html), enabling DevOps teams to reliably scale-out their MySQL infrastructure across commodity hardware, on-premise or in the cloud.

    One of the most significant enhancements is the introduction of Global Transaction Identifiers (GTIDs) where the primary development motivation was:

    - enabling seamless failover or switchover from a replication master to slave

    - promoting that slave to the new master

    - without manual intervention and with minimal service disruption.

    You can download the new MySQL Replication High Availability Guide (http://www.mysql.com/why-mysql/white-papers/mysql-replication-high-availability/) to

      [Read more...]
    Showing entries 1 to 4

    Planet MySQL © 1995, 2014, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

    Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.