Hello Kristian, Thank you for the reply. I want to make sure I understand this correctly. Is the planned design for crash safe replication to be that the slave must have the binary log enabled, so that slaves may use the GTID and XA to ensure that the slave and master are in sync? If the binary log is not enabled, then the slaves are not crash safe. Is my understanding correct?
Thanks -Zardosht On Fri, Oct 19, 2012 at 7:36 AM, Kristian Nielsen <[email protected]> wrote: > Zardosht Kasheff <[email protected]> writes: > >> What is that solution? Is the solution in MariaDB 5.5? Is there a way >> for another engine to also have this solution? > > 1. > http://www.percona.com/doc/percona-server/5.5/reliability/innodb_recovery_update_relay_log.html > > 2. Yes (I think it's even in MariaDB 5.1) > > 3. No, this is completely innodb-specific. > > My current plan for crash safe replication is that this will be part of > MDEV-26: > > https://mariadb.atlassian.net/browse/MDEV-26 > > This solution works by storing the state in the slave binlog, so it works with > any (XA-capable) engine. > > - Kristian. _______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
