enterprise-support team mailing list archive

[Grigory Rubtsov <rgbeast@xxxxxxxxx>]

Public bug reported:

Percona 5.6.15 release 63 inherits the upstream bug:
http://bugs.mysql.com/bug.php?id=68429

The bug is fixed in upstream today and documented as follows:

"When running the slave with --slave-parallel-workers at 1 or greater,
setting --slave-skip-errors=all caused the error log to be filled with
with instances of the warning -Slave SQL: Could not execute Query event.
Detailed error: ;, Error_code: 0-."

It affects me leading to daily multi-Gb log.

** Affects: mysql-server
     Importance: Unknown
         Status: Unknown

** Affects: percona-server
     Importance: Undecided
         Status: New

** Bug watch added: MySQL Bug System #68429
   http://bugs.mysql.com/bug.php?id=68429

** Also affects: mysql-server via
   http://bugs.mysql.com/bug.php?id=68429
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1282104

Title:
  Slave SQL: Worker 7 failed executing transaction ... Could not execute
  Query event. Detailed error: ;, Error_code: 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1282104/+subscriptions