Comments on: Towards a New Modular Replication Architecture

By: Drizzle Replication – The Command Message « join-fu!

Drizzle Replication – The Command Message « join-fu! — Sat, 13 Mar 2010 04:06:07 +0000

[...] in development, and a lot more. Before jumping in, you may want to read a quick overview about the concepts of Drizzle replication [...]

By: Eric Day

Eric Day — Fri, 03 Apr 2009 17:15:01 +0000

Looks great Jay! This is not only a great post for the replication design, but how Drizzle modules will work in general.

By: Jay Pipes

Jay Pipes — Fri, 03 Apr 2009 15:16:53 +0000

Excellent question, Sergey!

The end goal is to simply have create table map to InsertRecordEvent, alter table to UpdateRecordEvent, and drop table map to DeleteRecordEvent. With a real data-dictionary (materialized information_schema) then all a DDL statement would be is an event which changes the records in the information_schema…

For administrative commands, we have a similar dilemma though, and we’ve been discussing that issue on the mailing list:

https://lists.launchpad.net/drizzle-discuss/msg03523.html

Would be good to get your input on that!

Cheers!

jay

By: Mark Callaghan

Mark Callaghan — Fri, 03 Apr 2009 15:14:26 +0000

Jay,
I couldn’t agree with you more about the editorial on design. Today I am trying to debug some of our extensions to replication and I really, really do not enjoy dealing with that code. And in 5.1, more complexity has been added to it (RBR).

MySQL already supports sync replication, but only between a storage engine and the binlog. You need to provide more details on the new interfaces if we are to understand when sync and semi-sync can be done. For sync to be possible, methods are needed for Prepare and Commit as the storage and the implementation of the new interface are both resource managers.

By: Sergey Petrunya

Sergey Petrunya — Fri, 03 Apr 2009 13:31:49 +0000

InsertRecordEvent, DeleteRecordEvent, UpdateRecordEvent. What about table creation/alter/drop events?

By: Roland Bouman

Roland Bouman — Fri, 03 Apr 2009 10:08:28 +0000

Hi!

great post, thanks!

By: Stewart Smith

Stewart Smith — Fri, 03 Apr 2009 01:40:49 +0000

I think the most important thing in API design is not to be easy to use but to be hard to misuse.

e.g. the field->store methods can be said to be “easy to use” (at least for some things) but they are certainly very *easy* to misuse and end up with garbage or totally not what you expected.

Rusty’s API levels is a good read.