Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.0.10, 10.0.11, 10.0.12, 10.0.13
-
Fix Version/s: 10.0.18
-
Component/s: Storage Engine - InnoDB, Storage Engine - OQGRAPH
-
Labels:
-
Environment:CentOS 6.5: 2.6.32-431.29.2.el6.i686: CentOS-6.5-i386-minimal.iso: VMware ESXi = 1vCPU/8192MB
Description
I've spent about a week trying to build a stable instance of OQGRAPH for use by a webserver.
Finding that almost every-other external query results in InnoDB: Assertion failure. But no issues when using the CLI on localhost or a remote_host.
OK = localhost> SELECT * FROM oss.path; OK = remote_host> SELECT * FROM oss.path; NG = [localhost ~]# mysql -e 'SELECT * FROM oss.path;' NG = [remote_host ~]# mysql -h oqgrah_host -e 'SELECT * FROM oss.path;'
Note: The first query normally works, and subsequent queries fail. I've been using a stored procedure that normally restarts MariaDB, so every-other-query works.
OK = localhost> CALL oss.current_path(3); OK = remote_host> CALL oss.current_path(3); NG = [localhost ~]# mysql -e 'CALL oss.current_path(3);' NG = [remote_host ~]# mysql -h oqgrah_host -e 'CALL oss.current_path(3);'
–
This is a clean build, minimal CentOS, EPEL, & MariaDB from the repo. I've tried multiple MariaDB (default config) builds, even reverted to CentOS 6.3 to see if that would make a difference. I originally suspected the problem might with PHP, but no difference between mysql ' mysqli. Then I found the issue was reproducible from bash.
–
Attached you will find the syslog message, stored procedure, plus the DB schema and quick setup I have been working with. If you have any questions, please let me know.
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Hi Brian,
Could you please clarify some points regarding the problem description?
I assume lines starting with "OK" mean that the query went well, and "NG" – that the query failed?
In the summary, you say that external connection causes a crash – do you mean external as one coming from a remote host, or external as one executed in the batch mode (mysql -e ..)?
In the latter case, what is the significance of "remote host" vs "localhost"? It looks like both local and remote queries fail for you, do remote/local queries need to be executed in turn to trigger the assertion failure?
There is an open bug
MDEV-6345which looks similar, except that it required 2 connections to cause the failure, while in your case there seems to be only one; so it would be good to understand what exactly it takes to reproduce the problem you described.