Details
-
Bug
-
Status: Closed (View Workflow)
-
Trivial
-
Resolution: Fixed
-
10.0.8
-
None
Description
MySQL now uses LOST EVENTS incidents when s GRANT/REVOKE statement partially fails:
http://bugs.mysql.com/bug.php?id=68892
http://www.dbasquare.com/2013/04/09/granting-privileges-may-break-replication-in-mysql-5-6-10/
Replication is supposed to abort, and the discrepancy to be treated manually.
This works with 10.0 as a slave, but the error message which 10.0 writes into the error log and shows in SLAVE STATUS upon this incident is corrupted:
Last_Error: The incident LOST_EVENTS occured on the master. Message: error writing to the binary log�y�K
|
|
|
Slave SQL: The incident LOST_EVENTS occured on the master. Message: error writing to the binary log<E9>y<CD>K, Internal MariaDB error code: 1590
|
MySQL writes a clean message:
Last_SQL_Error: TThe incident LOST_EVENTS occured on the master. Message: error writing to the binary log
|
|
|
Slave SQL: The incident LOST_EVENTS occured on the master. Message: error writing to the binary log, Error_code: 1590
|
To reproduce:
# Set up replication MySQL 5.6 => MariaDB 10.0
|
|
|
# Execute on 5.6 master:
|
|
|
grant all on db.* to user1, user2;
|
revoke all on db.* from user1, user1;
|
# An error will occur (expected):
|
# ERROR 1141 (42000): There is no such grant defined for user 'user1' on host '%'
|
|
|
# On 10.0 slave, wait till replication aborts (expected), see the error message
|
revision-id: monty@askmonty.org-20140304183748-2wo25348vicg2qgp
|
revno: 4028
|
branch-nick: 10.0
|
Attachments
Issue Links
- relates to
-
MDEV-5705 replication testing: 5.6->10.0
-
- Stalled
-