Bug #75205 Master should write a LOST_EVENTS entry on xa commit after recovery.
| Submitted: | 13 Dec 2014 17:26 | Modified: | 27 Jan 2015 19:59 |
|---|---|---|---|
| Reporter: | Daniël van Eeden | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: XA transactions | Severity: | S2 (Serious) |
| Version: | 5.7.5-m15 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Backup, binlog, replication, xa | ||
[13 Dec 2014 17:26]
Daniël van Eeden
[18 Dec 2014 10:42]
Daniël van Eeden
http://dev.mysql.com/doc/refman/5.7/en/xa-restrictions.html "An implication is that XA cannot be used safely together with replication." That would also imply that it's not possible to use point in time recovery based on binlogs. Considering the common use cases for XA, not being able to fully recover all data is something I consider as a serious issue. (so Severity=S2 (Serious)) Some actions which can be done: - Make binlogs and XA work (e.g. remove the documented restriction) - Make sure replication and binlog restore don't silently ignore this (e.g. fix this bug) - Update the documentation to let people know XA and point-in-time recovery is not safe. - Get MySQL Enterprise Backup to emit a warning if XA is in active use
[21 Dec 2014 9:35]
Daniël van Eeden
As this also happens with TokuDB in 5.5.40-tokudb-7.5.3 this looks like an server issue.
[27 Jan 2015 19:59]
Sveta Smirnova
Thank you for the reasonable feature request.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.