[MDEV-12682] spider3.3.11 hit a bug! mysqld crash Created: 2017-05-04  Updated: 2017-05-05  Resolved: 2017-05-05

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Spider
Affects Version/s: 10.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: hiller1 Assignee: Jacob Mathew (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

mariadb10.1.22 spider3.3.11


 Description   

HI, I have compiled installed spider3.3.11 into MariaDB10.1.22 , but encountered a BUG, mysqld crash

for example:

MariaDB [test]> select `k` from sbtest limit 10;    
ERROR 2013 (HY000): Lost connection to MySQL server during query

---------------------------------------------------------------------------
error log:

170504 13:30:26 [ERROR] mysqld got signal 8 ;
 
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.
 
 
 
Query: select `k` from sbtest limit 10
 
 
 
170504 13:30:27 mysqld_safe Number of processes running now: 0
 
170504 13:30:27 mysqld_safe mysqld restarted


MariaDB [test]> select * from sbtest limit 1;
 
+----+---+---+----------------------------------------------------+
 
| id | k | c | pad                                                |
 
+----+---+---+----------------------------------------------------+
 
|  1 | 0 |   | qqqqqqqqqqwwwwwwwwwweeeeeeeeeerrrrrrrrrrtttttttttt |
 
+----+---+---+----------------------------------------------------+
 
1 row in set (0.00 sec)
 
 
 
MariaDB [test]> select id,k,c,pad from sbtest limit 1; 
+----+---+---+----------------------------------------------------+
 
| id | k | c | pad                                                |
 
+----+---+---+----------------------------------------------------+
 
|  1 | 0 |   | qqqqqqqqqqwwwwwwwwwweeeeeeeeeerrrrrrrrrrtttttttttt |
 
+----+---+---+----------------------------------------------------+
 
1 row in set (0.00 sec)
 
 
 
MariaDB [test]> select id from sbtest limit 1;        
ERROR 2013 (HY000): Lost connection to MySQL server during query
 
MariaDB [test]> select k from sbtest limit 1;  
ERROR 2006 (HY000): MySQL server has gone away
 
No connection. Trying to reconnect...
 
Connection id:    3
 
Current database: test
 
 
 
ERROR 2013 (HY000): Lost connection to MySQL server during query

--------------------------------------------------------------------------------------------------------------

CREATE TABLE `sbtest` (
 
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
 
  `k` int(10) unsigned NOT NULL DEFAULT '0',
 
  `c` char(120) NOT NULL DEFAULT '',
 
  `pad` char(60) NOT NULL DEFAULT '',
 
  PRIMARY KEY (`id`),
 
  KEY `k` (`k`)
 
) ENGINE=SPIDER DEFAULT CHARSET=utf8 COMMENT='wrapper "mysql", table "sbtest",srv "backend1"'



 Comments   
Comment by hiller1 [ 2017-05-04 ]

MariaDB [test]> select id from sbtest where id = 1;
----

id

----

1

----
1 row in set (0.00 sec)

MariaDB [test]> select id from sbtest limit 1;
ERROR 2013 (HY000): Lost connection to MySQL server during query
MariaDB [test]>

Comment by Jacob Mathew (Inactive) [ 2017-05-04 ]

I downloaded the source files for MariaDB 10.1.22 from GitHub. I then replaced the contents of the <server>/storage/spider directory with the latest Spider 3.3 source files from Kentoku's Spider fork on GitHub. I built everything.

I created a table with 10000 rows. Column k contained values ascending from 0 to 9999. Column c contained the default value ' ' in all rows. Column pad contained 'qqqqqqqqqqwwwwwwwwwweeeeeeeeeerrrrrrrrrrtttttttttt' in all rows. Here are the results from the various SELECT statements in the bug description:

MariaDB [test]> select `k` from sbtest limit 10;
 
+---+
 
| k |
 
+---+
 
| 0 |
 
| 1 |
 
| 2 |
 
| 3 |
 
| 4 |
 
| 5 |
 
| 6 |
 
| 7 |
 
| 8 |
 
| 9 |
 
+---+
 
10 rows in set (0.01 sec)
 
 
 
MariaDB [test]> select * from sbtest limit 1;
 
+----+---+---+----------------------------------------------------+
 
| id | k | c | pad                                                |
 
+----+---+---+----------------------------------------------------+
 
|  1 | 0 |   | qqqqqqqqqqwwwwwwwwwweeeeeeeeeerrrrrrrrrrtttttttttt |
 
+----+---+---+----------------------------------------------------+
 
1 row in set (0.01 sec)
 
 
 
MariaDB [test]> select id,k,c,pad from sbtest limit 1;
 
+----+---+---+----------------------------------------------------+
 
| id | k | c | pad                                                |
 
+----+---+---+----------------------------------------------------+
 
|  1 | 0 |   | qqqqqqqqqqwwwwwwwwwweeeeeeeeeerrrrrrrrrrtttttttttt |
 
+----+---+---+----------------------------------------------------+
 
1 row in set (0.00 sec)
 
 
 
MariaDB [test]> select id from sbtest limit 1;
 
+----+
 
| id |
 
+----+
 
|  1 |
 
+----+
 
1 row in set (0.01 sec)
 
 
 
MariaDB [test]> select k from sbtest limit 1;
 
+---+
 
| k |
 
+---+
 
| 0 |
 
+---+
 
1 row in set (0.00 sec)
 
 
 
MariaDB [test]> select id from sbtest limit 1;
 
+----+
 
| id |
 
+----+
 
|  1 |
 
+----+
 
1 row in set (0.00 sec)
 
 
 
MariaDB [test]> select id from sbtest limit 1;
 
+----+
 
| id |
 
+----+
 
|  1 |
 
+----+
 
1 row in set (0.00 sec)
 
 
 
MariaDB [test]> select id from sbtest limit 1;
 
+----+
 
| id |
 
+----+
 
|  1 |
 
+----+
 
1 row in set (0.00 sec)
 
 
 
MariaDB [test]> select id from sbtest limit 1;
 
+----+
 
| id |
 
+----+
 
|  1 |
 
+----+
 
1 row in set (0.01 sec)
 
 
 
MariaDB [test]>

I could not reproduce the problem.

Comment by hiller1 [ 2017-05-05 ]

Hello,Jacob Mathew :

I downloaded the spider today, https://github.com/Kentoku/Spider, found that the author has updated the error yesterday (Kentoku fix compiler reference error.), After re-build, now BUG resolved. Thank you.

Comment by Jacob Mathew (Inactive) [ 2017-05-05 ]

Hi hiller1. It is good to hear that you no longer encounter the problem after rebuilding with the latest Spider source code.

Since I could not reproduce the problem, I am closing the problem as unreproducible.

Generated at Thu Feb 08 07:59:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.