clustered index not passed for FK append
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
Fix Released
|
Medium
|
Seppo Jaakola | ||
5.1 |
Confirmed
|
Medium
|
Teemu Ollakka | ||
5.5 |
Fix Released
|
Medium
|
Seppo Jaakola |
Bug Description
Node crashed with following in error log:
120328 12:08:12 [ERROR] WSREP: clustered index not passed for FK append
InnoDB: unknown error code 11
120328 12:08:12 InnoDB: Assertion failure in thread 140671425816320 in file row0mysql.c line 649
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
09:08:12 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_
read_buffer_
max_used_
max_threads=1024
thread_count=6
connection_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x419c950
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7ff09e5d9e70 thread_stack 0x40000
/run/shm/
/run/shm/
/lib/x86_
/lib/x86_
/lib/x86_
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/run/shm/
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (41d5dc0): INSERT INTO child VALUES (101, 1)
Connection ID (thread ID): 16
Status: NOT_KILLED
Statements to reproduce:
CREATE TABLE parent
(
a INT PRIMARY KEY,
b INT,
INDEX idx_b(b)
) ENGINE=InnoDB
CREATE TABLE child
(
c INT,
d INT,
INDEX idx_d(d),
FOREIGN KEY (d) REFERENCES parent(b) ON DELETE CASCADE
) ENGINE=InnoDB
INSERT INTO parent VALUES (1, 1)
INSERT INTO child VALUES (101, 1)
Parent reference is not for primary key, and wsrep requires that. This PK requirement should be relaxed