MySQL crash at case of using "monitoring_bg_kind>=1"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Spider for MySQL |
Fix Released
|
Medium
|
Kentoku SHIBA |
Bug Description
MySQL crashes when execute any SQL After executing "CREATE TABLE" statement using "monitoring_
monitoring_
SQLを実行しようとするとMy
MySQL version: 5.5.8
Spider version: Spider 2.24 for 5.5.8
Using mysql-5.
Spider table:
node: n1(sid = 101)
CREATE TABLE salaries (
emp_no int(11) NOT NULL,
salary int(11) NOT NULL,
from_date date NOT NULL,
to_date date NOT NULL,
PRIMARY KEY (emp_no,from_date),
KEY emp_no (emp_no)
) ENGINE SPIDER PARTITION BY KEY(emp_no) PARTITIONS 2
(
PARTITION p1 COMMENT 'table "salaries", server "n5 n6", mbk "1", mkd "2", msi "102", link_status "1 1"',
PARTITION p2 COMMENT 'table "salaries", server "n7 n8", mbk "1", mkd "2", msi "102", link_status "1 1"'
);
Remote InnoDB partition tables:
node:n5(
CREATE TABLE salaries (
emp_no int(11) NOT NULL,
salary int(11) NOT NULL,
from_date date NOT NULL,
to_date date NOT NULL,
PRIMARY KEY (emp_no,from_date),
KEY emp_no (emp_no)
) ENGINE=InnoDB;
Monitoring Node: n2(sid=
servers:
+------
| Server_name | Host | Db | Username | Password | Port | Socket | Wrapper | Owner |
+------
| n1 | 127.0.0.1 | | msandbox | msandbox | 8359 | | mysql | |
| n2 | 127.0.0.1 | | msandbox | msandbox | 8360 | | mysql | |
| n3 | 127.0.0.1 | | msandbox | msandbox | 8361 | | mysql | |
| n4 | 127.0.0.1 | | msandbox | msandbox | 8362 | | mysql | |
| n5 | 127.0.0.1 | | msandbox | msandbox | 8363 | | mysql | |
| n6 | 127.0.0.1 | | msandbox | msandbox | 8364 | | mysql | |
| n7 | 127.0.0.1 | | msandbox | msandbox | 8365 | | mysql | |
| n8 | 127.0.0.1 | | msandbox | msandbox | 8366 | | mysql | |
+------
spider_
+------
| db_name | table_name | link_id | sid | server |
+------
| test | salaries#P#p1 | 0 | 102 | n2 |
| test | salaries#P#p1 | 0 | 103 | n3 |
| test | salaries#P#p1 | 0 | 104 | n4 |
| test | salaries#P#p2 | 0 | 102 | n2 |
| test | salaries#P#p2 | 0 | 103 | n3 |
| test | salaries#P#p2 | 0 | 104 | n4 |
| test | salaries#P#p1 | 1 | 102 | n2 |
| test | salaries#P#p1 | 1 | 103 | n3 |
| test | salaries#P#p1 | 1 | 104 | n4 |
| test | salaries#P#p2 | 1 | 102 | n2 |
| test | salaries#P#p2 | 1 | 103 | n3 |
| test | salaries#P#p2 | 1 | 104 | n4 |
+------
After create Spider Table,
I try to execute SELECT statement and MySQL crashes:
上記のスパイダーテーブルを作成
executed statement :
SELECT count(*) From salaries;
I get the following backtrace:
thd: 0xea902c0
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 = 0x4a6b80b0 thread_stack 0x40000
/usr/local/
/usr/local/
/lib64/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xeb192c0 = select count(*) from salaries
thd->thread_id=2
thd->killed=
The manual page at http://
information that should help you find out what is causing the crash.
using "monitoring_
monitoring_
using "monitoring_
and also In Spider 2.23 for 5.1.44 , this case don't occurred.
monitoring_
また、Spider2.
バグレポートありがとうございます。 だきます。
暫定対処版をアタッチさせていた