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 13

Displaying posts with tag: synchronization (reset)

How does the Replication Synchronization Checker Work?
+1 Vote Up -0Vote Down
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



  [Read more...]
New MySQL Utility: Replication Synchronization Checker
+1 Vote Up -0Vote Down
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 Features

Besides permitting the data consistency check of an active replication system, here are the main features of the mysqlrplsync utility:



  [Read more...]
Compare and Synchronize Databases with MySQL Utilities
Employee +2 Vote Up -0Vote Down
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







  [Read more...]
MySQL schema maintenance
+3 Vote Up -0Vote Down



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
  • [Q] Are there plans to administer MySQL Cluster with Workbench?
    [A] Not that we know of.

  • [Q] Can Workbench deal with user permission maintenance across servers? (especially in cases where development and production users










  [Read more...]
Maatkit version 1674 released
+0 Vote Up -0Vote Down

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.

What is new in Maatkit
+0 Vote Up -0Vote Down

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.

Maatkit version 1579 released
+0 Vote Up -0Vote Down

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.

Maatkit version 1417 released
+0 Vote Up -0Vote Down

Download Maatkit

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.

Progress on Maatkit bounty, part 3
+0 Vote Up -0Vote Down

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).

Progress on Maatkit bounty, part 2
+0 Vote Up -0Vote Down

Ironically, the Stream algorithm I wrote as the simplest possible syncing algorithm does what the much more efficient algorithm I wrote some time ago can't do: sync a table without a primary key, as long as there are no duplicate rows. In fact, it's so dumb, it will happily sync any table, even if there are no indexes.

The flash of inspiration I had on Friday has turned out to be good...

Progress on Maatkit bounty
+0 Vote Up -0Vote Down

My initial plans got waylaid! I didn't pull out the checksumming code first, because the code wasn't at all as I remembered it. Instead, I began writing code to handle the more abstract problem of accepting two sets of rows, finding the differences, and doing something with them. I'm ending up with a little more complicated system than I thought I would. However, it's also significantly simpler in some ways. Instead of just passing references to subroutines to use as callbacks, I'm object-ifying the entire synchronization concept...

Maatkit bounty begins tomorrow
+0 Vote Up -0Vote Down
Tomorrow is the first of five days I will spend working on mk-table-sync, the data synchronization tool I developed as part of Maatkit. The first thing I’ll do is pull the row-checksumming code out into a module and write a unit test suite for it. I’ll probably add the code to the module [...]
Proposed bounty on MySQL Table Sync features
+0 Vote Up -0Vote Down

I am considering taking some time off work to concentrate deeply on MySQL Table Sync, which has been getting usage in very large companies whose names we all know. There are a lot of bugs and feature requests outstanding for it. It is overly complex, needs a lot of work, and I can't do it in one-hour or even three-hour chunks. I need to focus on it. I'm considering asking for a bounty of $2500 USD for this. Please let me know what you think of this; it seems to be a successful way to sponsor development on some other projects, like Vim.

For the amount of time I think this will take, $2500 is far below my per-hour consulting rate; I considered setting the bounty higher, but I think this will be a fair amount.

I would not begin this project before December at the earliest, so there's some time

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

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.