-
Notifications
You must be signed in to change notification settings - Fork 5.5k
[native] Add native memory pool reclaimer priority #25325
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
Conversation
|
This pull request was exported from Phabricator. Differential Revision: D76368381 |
|
depends on #25318 |
|
CC: @aditi-pandit @czentgr This is waiting for velox advance PR #25318 |
|
This pull request was exported from Phabricator. Differential Revision: D76368381 |
49e4914 to
f0a00f8
Compare
|
@amitkdutta : This looks like a new property... Is something existing broken for you folks until this makes in ? |
steveburnett
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGMT! (docs)
Pull branch, local doc build, looks good. Thanks!
Currently our production set up kills queries without priority, which is problematic. We want to roll out a feature where query can be killed by prirority. This is a major reliablity problem. |
|
@amitkdutta : That makes sense. Its definitely an improvement. It doesn't sound like it's fixing a regression though. Lets try to isolate which Velox change broke the build. That build is just bad... its possible nothing Prestissimo will run with it. |
|
@amitkdutta : Heard that Christian gave you a patch. Lets try it. I've removed the hold on the other PR. |
|
This pull request was exported from Phabricator. Differential Revision: D76368381 |
f0a00f8 to
7127750
Compare
|
@amitkdutta @aditi-pandit - Updated. thanks for fixing the build. |
Summary: Pull Request resolved: prestodb#25325 add native_query_memory_reclaimer_priority property Used for victim selection when killing queries to avoid worker OOM Differential Revision: D76368381
|
This pull request was exported from Phabricator. Differential Revision: D76368381 |
7127750 to
e215718
Compare
amitkdutta
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @singcha
Summary: Pull Request resolved: prestodb#25325 add native_query_memory_reclaimer_priority property Used for victim selection when killing queries to avoid worker OOM Differential Revision: D76368381
Summary: Pull Request resolved: prestodb#25325 add native_query_memory_reclaimer_priority property Used for victim selection when killing queries to avoid worker OOM Differential Revision: D76368381
Description
Adds
native_query_memory_reclaimer_priorityproperty.This is used to pass query memory reclaimer priority to Velox. Velox memory manager uses specified property to determine which query to kill when system runs on memory pressure.
Motivation and Context
When native worker runs into memory pressure, it starts killing queries to avoid cgroup OOM/process crash. When choosing the victim, we want to specify which queries are more likely to be chosen as victim. This change enables specifying memory reclaimer priority which is used for memory kills.
It could be further extended to choose which queries reclaimer spills first, which is outside the scope of this PR
Impact
Critical queries are less likely to be killed in a cluster
Test Plan