As I understand it, it is not quite that...
The transaction must get into the Slave's relay log before returning from the COMMIT.
(That's not the same as "committing".)
> -----Original Message-----
> From: Zardosht Kasheff [mailto:zardosht@stripped]
> Sent: Wednesday, October 03, 2012 8:16 AM
> To: internals@stripped
> Subject: making a storage engine crash safe on a slave in MySQL 5.6
>
> Hello all,
>
> I read that InnoDB is now crash safe on slaves in MySQL 5.6. I
> understand that a way they do this is on committing a transaction on a
> slave, they store the binary log position in an InnoDB table (which
> makes that information transactionally maintained). I also understand
> that this position is stored for each database, as databases may apply
> the replication log in parallel.
>
> Upon recovery of a slave, how does InnoDB report to MySQL where the
> replication log should resume?
>
> Can another storage engine similarly make itself crash safe on a slave?
> Will there be any issues with multiple storage engines doing so?
>
> Thanks
> -Zardosht
>
> --
> MySQL Internals Mailing List
> For list archives: http://lists.mysql.com/internals
> To unsubscribe: http://lists.mysql.com/internals
