-
Notifications
You must be signed in to change notification settings - Fork 9.2k
YARN-11646. Do not ignore zero memory capacity config in QueueCapacityConfigParser. #6433
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
…yConfigParser. Change-Id: Id00a5382d982dcf33ec8a3769fc33419b660968b
c0191da to
29d5dd4
Compare
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
Change-Id: I4dd06e96cc6bb2ac63f9ef3062bba3e8d0f8509e
|
🎊 +1 overall
This message was automatically generated. |
|
Thanks @tomicooler for this change! LGTM! |
brumi1024
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 @tomicooler for the patch, @K0K0V0K for the review. LGTM, merging to trunk.
… QueueCapacityConfigParser. (apache#6433) Change-Id: Ibbecee0193bb9af09df4d227bc52efbc322a37c7 (cherry picked from commit 436ef1676ec0f083fc0d7057f902569cecb25ebb)
Change-Id: Id00a5382d982dcf33ec8a3769fc33419b660968b
Description of PR
There is no reason to ignore the configured capacity if the memory is 0 in the configuration.
It makes it impossible to configure a zero absolute resource capacity.
Example:
How was this patch tested?
Ran the unit tests.
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?