Previous episodes:
MySQL replication in action - Part 1: GTID &
CoMySQL replication in action - Part 2 - Fan-in
topologyMySQL replication in action - Part 3 - All-masters
P2P topology
Introducing star topology.In all-masters P2P topologies, we have
seen that we have a way of deploying a topology where all nodes
are masters, and achieve better efficiency and stability than
ring topologies. That …
We recently introduced 'mysqlrplsync' in MySQL Utilities
release-1.4.2 RC. This new utility allows users to check the data
consistency of an active replication system. In this blog we
provide more details about how 'mysqlrplsync' works.
In an active replication topology, slaves may be slightly behind
the master in processing events. Depending on the workload and
capabilities of each slave, transactions may be applied at
different times. Should this occur and something untoward happen
to one of the slaves (such as a user making a manual change
directly on the slave), a synchronization process may be required
to ensure that the slaves have the same data - to manually catch
up all of the slaves that are behind the master.
The strategy we choose was to build on the top of the replication
process and makes use of GTIDs; it works independently of the
binary log format (row, statement, or mixed) and does not create
any new data …
We are very happy to introduce an new MySQL utility called
'mysqlrplsync' that can check the data consistency of an active
replication system. This utility is one of the new utilities
included in MySQL Utilities release-1.4.2 RC. The other utility
is the multi-source replication utility, mysqlrplms.
In a nutshell, the mysqlrplsync utility allows you to check the
data consistency between servers in an active replication system.
The utility reports missing databases and tables as well as data
differences (per table) between the servers. A sophisticated
synchronization algorithm that utilizes a table checksum is
applied on the active replication servers to locate differences
in the data.
Main FeaturesBesides permitting the data consistency check of an
active replication system, here are the main features of the
mysqlrplsync utility:
The mysqldiff and mysqldbcompare utilities were designed to
produce a difference report for objects and in the case of
mysqldbcompare the data. Thus, you can compare two databases and
produce a report of the differences in both object definitions
and data rows.
While that may be very useful, would it not be much more useful
to have the ability to produce SQL commands to transform
databases? Wait no longer! The latest release of MySQL Utilities
has added the ability to generate SQL transformation statements
by both the mysqldiff and mysqldbcompare utilities.
To generate SQL transformations in either utility, simply use the
--sql option to tell the utility to produce the statements.
Object Transformations with mysqldiff
If you would like to compare the schema of two databases (the
objects and their definitions), mysqldiff can do that for you and
produce a difference report …
|
|
At CodeBits I had my first session about MySQL schema maintenance. I covered the basic command line possibilities before coming to the recommended tool, MySQL Workbench. The slides are available at slideshare. |
Interesting questions: ([updated] with answers from the
development team
This release contains bug fixes and new features. Click through to the full article for the details. I'll also write more about the changes in a separate article.
My posts lately have been mostly progress reports and release notices. That's because we're in the home stretch on the book, and I don't have much spare time. However, a lot has also been changing with Maatkit, and I wanted to take some time to write about it properly.
This release contains bug fixes and new features. The biggest new feature, in my opinion, is a new sync algorithm for mk-table-sync. Now you can sync any table with an index more efficiently than previously. This is the return of the speed I promised earlier. (Though I haven't yet benchmarked it; I am very short on time these days. Your benchmarks and other contributions are welcome).
I'm finally feeling like the table sync tool is getting in good shape!
Changelog etc is in the full article.
Thanks again to all the great sponsors for my week of work on the kit!
This is the long-awaited "Baron worked on table sync" release. Hooray!
Please read the full blog post for important (very important!) information.
This is the last day I'm taking off work to hack on mk-table-sync, and I thought it was time for (yet another) progress report. Here's what I have done so far. (Click through to the full article to read the details).