MySQL crashes during an ALTER TABLE
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Spider for MySQL |
Fix Released
|
High
|
Kentoku SHIBA |
Bug Description
Hi,
MySQL is crashing when doing an ALTER TABLE on an existing innodb table with existing data
ALTER TABLE table
ENGINE=SPIDER CONNECTION='table "table", user "root"'
PARTITION BY LIST(id)
(PARTITION p0 values in (0, 3, 6) COMMENT = 'host "m0", port "3306"' ENGINE = SPIDER,
PARTITION p1 values in (1, 4, 7) COMMENT = 'host "m1", port "3306"' ENGINE = SPIDER,
PARTITION p2 values in (2, 5, 8) COMMENT = 'host "m2", port "3306"' ENGINE = SPIDER);
I get the following backtrace:
thd: 0x39d5abe0
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 = 0x7f0b4a520ea0 thread_stack 0x30000
/usr/bin/
/usr/bin/
/lib64/
/usr/bin/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x7f0b3c004a50 is an invalid pointer
thd->thread_id=8
thd->killed=
The manual page at http://
information that should help you find out what is causing the crash.
Changed in spiderformysql: | |
assignee: | nobody → Kentoku SHIBA (kentokushiba) |
importance: | Undecided → High |
Changed in spiderformysql: | |
status: | New → In Progress |
Hi,
Thank you for reporting a bug.
This bug was fixed and released in Spider 2.24.
Thanks,
Kentoku