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

Query exceeded max memory size when like operate #11683

Closed
zhaiyuyong opened this issue Oct 10, 2018 · 10 comments
Closed

Query exceeded max memory size when like operate #11683

zhaiyuyong opened this issue Oct 10, 2018 · 10 comments
Labels

Comments

@zhaiyuyong
Copy link

zhaiyuyong commented Oct 10, 2018

select * from a.table_1 where pt='2018-10-09' and id like '%123456' limit 10;
Query 20181010_060653_03859_wve7n failed: Query exceeded max memory size of 500GB
@findepi
Copy link
Contributor

findepi commented Oct 10, 2018

Have a look at query JSON in the Web UI. It will show you where all the memory allocations were accounted.

@zhaiyuyong
Copy link
Author

zhaiyuyong commented Oct 10, 2018

image

image

image

@findepi
Copy link
Contributor

findepi commented Oct 10, 2018

@zhaiyuyong i see you found the json (https://user-images.githubusercontent.com/4199724/46720753-fc558a00-cca3-11e8-9630-5ed64c8f1b84.png).
now you need to find the operator that has mem allocations.

@zhaiyuyong
Copy link
Author

@findepi
image

@findepi
Copy link
Contributor

findepi commented Oct 10, 2018

This might be incorrect accounting of the memory. What is Presto version? What is the file format?

@zhaiyuyong
Copy link
Author

file format:ORC
presto version:0.203

@nezihyigitbasi
Copy link
Contributor

I recommend you to try the latest version as there have been memory tracking-related fixes since 0.203.

@zhaiyuyong
Copy link
Author

@nezihyigitbasi could you provide an id of the issue?

@tsuxia
Copy link

tsuxia commented Feb 19, 2019

Was wondering if this issue should be closed or not?

@stale
Copy link

stale bot commented Jun 23, 2021

This issue has been automatically marked as stale because it has not had any activity in the last 2 years. If you feel that this issue is important, just comment and the stale tag will be removed; otherwise it will be closed in 7 days. This is an attempt to ensure that our open issues remain valuable and relevant so that we can keep track of what needs to be done and prioritize the right things.

@stale stale bot added the stale label Jun 23, 2021
@stale stale bot closed this as completed Jul 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants