Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: EXPLAIN query Q4, MySQL server has gone away #727

Closed
2 of 3 tasks
davidshiz opened this issue Oct 14, 2022 · 4 comments · Fixed by #812
Closed
2 of 3 tasks

bug: EXPLAIN query Q4, MySQL server has gone away #727

davidshiz opened this issue Oct 14, 2022 · 4 comments · Fixed by #812
Assignees
Labels
A-bug Something isn't working prio: high High priority

Comments

@davidshiz
Copy link
Collaborator

Have you read the Contributing Guidelines on issues?

Please confirm if bug report does NOT exists already ?

  • I confirm there is no existing issue for this

Describe the problem

EXPLAIN TPCH Q4 query, MySQL server has gone away

mysql> explain select o_orderpriority, count(*) as order_count from orders where o_orderdate >= date '1993-07-01' and o_orderdate < date '1993-07-01' + interval '3' month and exists ( select * from lineitem where l_orderkey = o_orderkey
and l_commitdate < l_receiptdate ) group by o_orderpriority order by o_orderpriority limit 100;
ERROR 2013 (HY000): Lost connection to MySQL server during query
mysql> 2022-10-14T10:15:22.957293Z mysqld_safe Number of processes running now: 0
2022-10-14T10:15:22.962802Z mysqld_safe mysqld restarted

Expected behavior

No response

How To Reproduce

The data generated by DBGen
./dbgen -s 1
the size of the test database is 1GB
EXPLAIN TPCH Q4 query, MySQL server has gone away

explain select
	o_orderpriority,
	count(*) as order_count
from
	orders
where
	o_orderdate >= date '1993-07-01'
	and o_orderdate < date '1993-07-01' + interval '3' month
	and exists (
		select
			*
		from
			lineitem
		where
			l_orderkey = o_orderkey
			and l_commitdate < l_receiptdate
	)
group by
	o_orderpriority
order by
	o_orderpriority
limit 100;

Environment

ubuntu@ubuntu:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.4 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.4 LTS"
VERSION_ID="20.04"

ubuntu@ubuntu:~$ /stonedb57/install/bin/mysqld --version
/stonedb57/install/bin/mysqld  Ver 5.7.36-StoneDB-debug for Linux on x86_64 (build-)
build information as follow:
        Repository address: https://github.com/stoneatom/stonedb.git:stonedb-5.7-dev
        Branch name: stonedb-5.7-dev
        Last commit ID: 30d45ddde
        Last commit time: Date:   Thu Oct 13 14:05:57 2022 +0800
        Build time: Date: Thu 13 Oct 2022 08:24:21 AM UTC

Are you interested in submitting a PR to solve the problem?

  • Yes, I will!
@davidshiz davidshiz added the A-bug Something isn't working label Oct 14, 2022
@davidshiz davidshiz added this to the stonedb_5.7_v1.0.1 milestone Oct 14, 2022
@adofsauron
Copy link
Collaborator

This is the debug version, under the debug version there are debug assertions, and you need to use the release version to continue testing

Ver 5.7.36-StoneDB-debug

@adofsauron
Copy link
Collaborator

adofsauron commented Oct 17, 2022

the similar as #726

@adofsauron
Copy link
Collaborator

The release version does not have this problem

@davidshiz
Copy link
Collaborator Author

Debug version need to be fixed

@RingsC RingsC assigned DandreChen and unassigned adofsauron Oct 18, 2022
@RingsC RingsC added the prio: high High priority label Oct 18, 2022
DandreChen added a commit to DandreChen/stonedb that referenced this issue Oct 26, 2022
Eplain query Q4 lead to crash,because assert(join == NULL) in SELECT_LEX::optimize() function.
the root cause is that the new join is not released. we can use sl->cleanup(true) to release it
DandreChen added a commit to DandreChen/stonedb that referenced this issue Oct 26, 2022
Eplain query Q4 lead to crash,because assert(join == NULL) in SELECT_LEX::optimize() function.
the root cause is that the new join is not released. we can use sl->cleanup(true) to release it
DandreChen added a commit to DandreChen/stonedb that referenced this issue Oct 26, 2022
Eplain query Q4 lead to crash,because assert(join == NULL) in SELECT_LEX::optimize() function.
the root cause is that the new join is not released. we can use sl->cleanup(true) to release it
@mergify mergify bot closed this as completed in #812 Oct 26, 2022
mergify bot pushed a commit that referenced this issue Oct 26, 2022
Eplain query Q4 lead to crash,because assert(join == NULL) in SELECT_LEX::optimize() function.
the root cause is that the new join is not released. we can use sl->cleanup(true) to release it
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-bug Something isn't working prio: high High priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants