[MDEV-4624] Galera Crash Created: 2013-06-07 Updated: 2013-08-28 Resolved: 2013-08-28 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.29-galera |
| Fix Version/s: | 5.5.32-galera |
| Type: | Bug | Priority: | Critical |
| Reporter: | Will Fong | Assignee: | Seppo Jaakola |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | galera, replication | ||
| Environment: |
RHEL |
||
| Attachments: |
|
| Description |
|
We are in the process of migrating to a MariaDB Galera cluster from a MySQL 5.1 Replication environment. The first step is to use one Galera node as a replication slave to the existing environment. This process was running smoothly until it started crashing with the attached stack trace. Restarting the node did not solve the issue. Stopping the slave process (skip-slave-start) will allow the node to start, but crashes again when we resume replication. |
| Comments |
| Comment by Seppo Jaakola [ 2013-06-07 ] |
|
This looks quite similar as case reported here: https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1134892 |
| Comment by Seppo Jaakola [ 2013-06-07 ] |
|
I can confirm that this issue is a duplicate of the one linked above. The problem happens when replicating a transaction which modifies tables with cascading foreign key constraints. Can you pinpoint which parent-child table pair were part of this crashing transaction? If so, please show the table definitions for inspection. Also, attach your my.cnf |
| Comment by Seppo Jaakola [ 2013-06-07 ] |
|
The revision used in this case is #3390 in mariadb-galera branch and is tagged with: mariadb-galera-5.5.29. |
| Comment by Will Fong [ 2013-06-11 ] |
|
Hello. Attached is the schema for the transaction in question: MariaDB [ped]> show create table 1\G
MariaDB [ped]> show create table 2\G
MariaDB [ped]> show create table 3\G
MariaDB [ped]> show create table 6\G
The transaction contains row-based DELETE statements on tables 1 and 3. I'll grab the my.cnf file as soon as possible. Thanks, |
| Comment by Seppo Jaakola [ 2013-06-12 ] |
|
I was able to reproduce according to suggested scenario: 1. Start standard replication from MySQL master to first Galera node. This happened with 5.5.29 release, but not anymore with 5.5.31 RC. I have a targeted fix for 5.5.29, which I probably merge for 5.5.31 during today. |
| Comment by Seppo Jaakola [ 2013-06-13 ] |
|
Merged last fixes related to this issue in revision: http://bazaar.launchpad.net/~maria-captains/maria/maria-5.5-galera/revision/3400 |
| Comment by Rasmus Johansson (Inactive) [ 2013-08-28 ] |
|
Reopened to be able to move to correct fix version |