Hi,

As I understand it, Galera doesn't work through the pluggable storage engine API, so adding it via the engine interface is not an option.  It intercepts the binary log capture process, implements a global transaction identifier and wire transaction state prototocol (wsrep), and is tightly integrated with InnoDB so as to trigger deadlocks on incoming replication write conflicts.  It is not possible to use Galera with TokuDB or MyISAM for this reason (though MyISAM is technically supported, it is not a good idea).  Because it only works with InnoDB and MyISAM (barely), it makes sense (at least to me) to make it a separate package.

Just my $.02


On Mon, Feb 10, 2014 at 11:11 PM, Honza Horak <hhorak@redhat.com> wrote:
Hi guys,

my Google-foo is poor today and I can't find any discussion about "inclusion of Codership's Galera patch to standard code-source of MariaDB". I'd like to see that one could just use the wresp plugin and have a working Galera cluster (even if that would mean to introduce new engine) without having another instance of the package.

Is that technically possible at all and if so, are there any thoughts like this?

Thanks,
Honza

_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to     : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp