Crash triggered with mysqldump single-transaction
Description
Environment
OS: Ubuntu 16.04.5 LTS
Package: percona-xtradb-cluster-server-5.7 - 5.7.24-31.33-1.xenial
Attachments
- 09 Jan 2019, 01:19 PM
- 09 Jan 2019, 01:09 PM
duplicates
Smart Checklist
Activity
Krunal Bauskar February 4, 2019 at 7:33 AM
commit 9b133899309178b7f981569172ce52fc5d1d67b2
Merge: eb0b8aed2ac dcd2728b2cf
Author: Krunal Bauskar <krunal.bauskar@percona.com>
Date: Mon Feb 4 13:01:02 2019 +0530
Merge pull request #739 from kennt-percona/5.7-pxc-2345
https://perconadev.atlassian.net/browse/PXC-2345#icft=PXC-2345 : Crash triggered with mysqldump single-transaction
commit dcd2728b2cfc86e583bd10c7fb6b30999a4dcb8a
Author: Kenn Takara <kenn.takara@percona.com>
Date: Mon Jan 21 02:49:14 2019 -0800
https://perconadev.atlassian.net/browse/PXC-2345#icft=PXC-2345 : Crash triggered with mysqldump single-transaction
Issue
Running 'mysqldump --single-transaction' on a running PXC
server causes a crash.
Solution
If WSREP is enabled, skip over the consistent snapshots.
This was regression from the previous version.
Lalit Choudhary January 15, 2019 at 7:43 AM
Hello Dev,
Thank you for the report.
Described behavior already reported and verified in our bugs database at https://perconadev.atlassian.net/browse/PXC-2346#icft=PXC-2346. Therefore I am closing this report as a duplicate.
Please subscribe for the original bug report to receive updates in time.
Lorraine Pocklington January 9, 2019 at 5:21 PM
Issue has also been reported today via freenode as being seen on 5.7.24-31.33-1.jessie and that when setting bin_log=binlog and server-id=1 in my config mysqldump runs without problems
Internal to Percona slack link that just says the same
Dave Fortuijn January 9, 2019 at 2:02 PM
We downgraded to 5.7.23-31.31-2.xenial and the issue does not occur in this version.
Details
Details
Assignee
Reporter
Time tracking
Affects versions
Priority
HighSmart Checklist
Open Smart Checklist
Smart Checklist
We are able to trigger a crash when we use --single-transaction with mysqldump. We tracked the issue down to the setting 'log_bin'. When removing 'log_bin' from the my.cnf we crash mysql by using this command:
mysqldump -u user --single-transaction mysql > mysql.sql
mysqldump: Couldn't execute 'START TRANSACTION /*!40100 WITH CONSISTENT SNAPSHOT */': Lost connection to MySQL server during query (2013)
When 'log_bin' is enabled in the my.cnf, it does not trigger the crash. Enclosed document contains the stack trace from the mysqld log.