-
Notifications
You must be signed in to change notification settings - Fork 700
Unexpected "Mkql memory limit exceeded" problem after the query failure (tpcds q14 & q24 problems) #6832
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
Milestone
Comments
Part of the log of the failing request:
The top-level error message looks like:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As I see from the benchmark results, there is a problem when after the "Mkql memory limit exceeded" error the next query can fail with a different limit or even without extra memory allocations. Need an investigation on this and fix for sure.
Failed:
: Error: Mkql memory limit exceeded, limit: 5358747648, host: d-c0f9g9voc9o4o1m4sj49-ydb-testing-sas-0-14, canAllocateExtraMemory: 1, memory manager details: TxResourcesInfo{ Memory initially granted resources: 2097152, extra allocations 10718543872, execution units: 0, started at: 2024-07-14T13:31:06.488128Z }, code: 2029запрос q13 падает вот так
execution units = 0 эт ладно, но оно пишет
extra allocations 10718543872 - это 10 гб
q14
Failed:
: Error: Mkql memory limit exceeded, limit: 31457280, host: d-c0f9g9voc9o4o1m4sj49-ydb-testing-sas-0-16, canAllocateExtraMemory: 1, memory manager details: TxResourcesInfo{ Memory initially granted resources: 13107200, extra allocations 125829120, execution units: 0, started at: 2024-07-14T13:32:39.948055Z }, code: 2029The text was updated successfully, but these errors were encountered: