RE: Here"s an Idea for Re-Syncing Master and Slave During Production Hours without Interrupting User

Hi Baron,

> I'm the primary author of Maatkit. =20

Awkward... :-)

> What can I say -- you could go buy a commercial off-the-shelf tool=20
> and believe the song and dance they feed you about the tool=20
> being perfect. =20

There's not a single commercial software solution in our toolbox. We're
big fans of CentOS, LVS, heartbeat, ldirectord, tomcat, MySQL, Xen,
pureFTP, and more. We've been happy with the performance and reliability
of all of our FOSS tools. I'm definitely not a Kool-aid drinker when it
comes to commercial product marketing.

> At least with Maatkit, you get transparency. We make a concerted=20
> effort to update the RISKS section of each tool with each release, so
there=20
> is full disclosure.

Fair enough, but I still found the warnings a little too scary. A more
complete explanation of the exact nature of the bugs and the exact
circumstances under which I should be concerned about triggering them
would have increased my comfort level. =20

> I think Maatkit is by far the best solution for live master-slave sync

> in most real-world situations.

We'll give it another look.

--
Eric Robinson



Disclaimer - December 9, 2009=20
This email and any files transmitted with it are confidential and =
intended solely for Baron Schwartz,Gavin Towey,Tom =
Worster,mysql@lists.mysql.com. If you are not the named addressee you =
should not disseminate, distribute, copy or alter this email. Any views =
or opinions presented in this email are solely those of the author and =
might not represent those of . Warning: Although has taken reasonable =
precautions to ensure no viruses are present in this email, the company =
cannot accept responsibility for any loss or damage arising from the use =
of this email or attachments.=20
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Re: Here"s an Idea for Re-Syncing Master and Slave During Production

Hi Eric,

>> At least with Maatkit, you get transparency. =A0We make a concerted
>> effort to update the RISKS section of each tool with each release, so
> there
>> is full disclosure.
>
> Fair enough, but I still found the warnings a little too scary. A more
> complete explanation of the exact nature of the bugs and the exact
> circumstances under which I should be concerned about triggering them
> would have increased my comfort level.

I've made a note to review these, because the ones I checked have kind
of drifted from their original purity. I updated the RISKS section
for mk-table-sync the other day. I checked it and agreed with you --
it didn't distinguish between cases where there is actually a risk, or
cases where the tool would just refuse to work (which isn't a risk
IMO). And it sounded ambiguously scary in a don't-blame-us,
we're-avoiding-your-eyes kind of way because of passive voice. You
can see my changes here:
http://code.google.com/p/maatkit/source/detail?r=3D5269 I think that's
a pretty realistic balanced statement of risk: you are playing with a
powerful tool, so learn how to use it first.

Thanks for the feedback! BTW, there's also a Maatkit mailing list
that I watch closely: http://groups.google.com/group/maatkit-discuss

- Baron

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg