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

ERROR 1105 (HY000): unknown error: no memory available #969

Closed
ajnavarro opened this issue Oct 10, 2019 · 6 comments
Closed

ERROR 1105 (HY000): unknown error: no memory available #969

ajnavarro opened this issue Oct 10, 2019 · 6 comments
Labels
bug Something isn't working

Comments

@ajnavarro
Copy link
Contributor

ajnavarro commented Oct 10, 2019

Setting MAX_MEMORY to 1024 and executing the following query:

SELECT 
	COUNT(blob_hash),        
	commit_hash 
FROM ref_commits 
NATURAL JOIN commits 
NATURAL JOIN commit_blobs 
WHERE ref_name = 'HEAD' 
GROUP BY commit_hash;

I get the following error:

ERROR 1105 (HY000): unknown error: no memory available

This is OK, but if I execute the query again, it can be executed as usual.

If it can be executed, it should be executed the first time too.

It took 36362 rows in set (11 min 27.23 sec)

@ajnavarro ajnavarro added the bug Something isn't working label Oct 10, 2019
@erizocosmico
Copy link
Contributor

What is the dataset?

@ajnavarro
Copy link
Contributor Author

sorry, I forgot to mention it: bblfsh + src-d organizations.

@erizocosmico
Copy link
Contributor

erizocosmico commented Oct 11, 2019

I've downloaded the dataset and tried to reproduce with 1024 and other different amounts and whenever it errors the first time, it errors all other times for me.

Did you try with the siva files collected by gitcollector or manually download? Perhaps if they were not siva, the memory footprint will change.

@ajnavarro
Copy link
Contributor Author

They are siva files downloaded using gitcollector.

@erizocosmico
Copy link
Contributor

I used those too and could not reproduce

@ajnavarro
Copy link
Contributor Author

I'm not able to reproduce it again, closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants