Bug #69126 Setting slave_parallel_workers=0 after a skipping an error crashes MySql

Submitted: 2 May 2013 17:43 Modified: 24 May 2013 11:52
Reporter: Liam Hewitt Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Replication Severity:S1 (Critical)
Version:5.6.11 OS:Solaris
Assigned to: CPU Architecture:Any
Tags: MySQL, parallel, replication, slave, workers

[2 May 2013 17:43] Liam Hewitt 
Description:
After a replication error that caused replication to stop, setting slave_parallel_workers=0 and trying to start slave crashes the MySql server, which then restarts itself.

How to repeat:
Receive replication error that halts replication.

set global slave_parallel_workers=0;

SET GLOBAL sql_slave_skip_counter = 1;

start slave;
[2 May 2013 17:46] Shane Bester 
Please upload the mysql error log containing the crash information?
[2 May 2013 18:05] Liam Hewitt 
We had several crashed tables and a few other issues here, but I don't believe that is related.
[2 May 2013 18:39] Shane Bester 
This is looking like a duplicate of the bug:
http://bugs.mysql.com/bug.php?id=68506
[24 May 2013 6:57] MySQL Verification Team 
Thank you for the bug report, duplicate of http://bugs.mysql.com/bug.php?id=68506

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.054 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.