maria-developers team mailing list archive
Mailing list archive
Re: Tungsten Replicator and MariaDB
On Sat, Jun 20, 2009 at 12:20 PM, MARK CALLAGHAN <mdcallag@xxxxxxxxx> wrote:
> On Sat, Jun 20, 2009 at 11:16 AM, Robert
> Hodges<robert.hodges@xxxxxxxxxxxxxx> wrote:
> > Hi All,
> > I have the same question as Mark, namely: what is the prioritized list
> > possible improvements to replication? To answer Mark's other question,
> > improving replication is work that we (Continuent) would be willing to
> > fund. Improvements in this area seem like a great way for MariaDB to
> > differentiate itself. We would like to help create the list of likely
> > for improvement both in terms of benefits to users as well as how
> > fixes are.
> > Here are a few items that I have run into during work in the MySQL
> > They may be different from other people as we are parsing the binlog
> > directly, which is not something that the average user does regularly.
> > * Event checksums. Binlog corruption does not happen too often but it's
> > when it does. I got it last week during a customer demo. :(
> > * Column names in table map events. Right now it's just numbers. Not
> > for filtering SQL or replication to other databases.
> > * Keys. Update events in row replication use before/after images but do
> > specify keys. This is problematic in a number of cases.
> > Global transaction IDs and semi-synchronous replication support would
> > be high on my list of feature additions for general usability. Fixes for
> > serious bugs would also be very welcome.
> > Cheers, Robert
> > P.s., Mark, do you have a pointer to the extensibility bug(s)?
Sounds like you're asking about 37466 <http://bugs.mysql.com/?id=37466>.
> Justin or Mats might know the bug numbers. The fix for this should be
> included in the launchpad branch Justin created for global group ids
> -- https://code.launchpad.net/~jtolmer/mysql-server/global-trx-ids
Yes, my launchpad branch has the fix for 37466. There are actually several
places which needed to be fixed including changing the slave to no longer
write stop events to the relay log.
My branch also has several other fixes; event checksums, global transaction
ID based recovery of replication positions after a slave crash and my fixes
for 38826 <http://bugs.mysql.com/?id=38826> and
are a bit different from the official ones.
> Mark Callaghan