YARN-11133. YarnClient gets the wrong EffectiveMinCapacity value#4280
YARN-11133. YarnClient gets the wrong EffectiveMinCapacity value#4280hemanthboyina merged 6 commits intoapache:trunkfrom zhuzilong2013:YARN-11133
Conversation
|
💔 -1 overall
This message was automatically generated. |
|
@aajisaka - Please review this PR. Thanks. |
hemanthboyina
left a comment
There was a problem hiding this comment.
thanks for raising PR @zhuzilong2013 , can you extend an Unit Test for your change
|
@hemanthboyina hemanthboyina Thanks for your patient guidance, I have extend an Unit Test for my change. Please review it. Thanks. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
@hemanthboyina I think it's all correct. Please review it. Thanks. |
|
thanks for the contribution @zhuzilong2013 , thanks for the review @aajisaka |
(cherry picked from commit 79cc0ca)
…che#4280) * Update QueueConfigurationsPBImpl.java * Update TestPBImplRecords.java * Update TestPBImplRecords.java * Update TestPBImplRecords.java * Update TestPBImplRecords.java
Description of PR
It calls the QueueConfigurations#getEffectiveMinCapacity to get the wrong value when I use the YarnClient. I found some bugs with QueueConfigurationsPBImpl#mergeLocalToBuilder. ConfiguredMinResource was incorrectly assigned to effMinResource. This causes the real effMinResource to be overwritten and configuredMinResource is null.
JIRA: YARN-11133
How was this patch tested?
Test in a production environment
For code changes:
Call the correct method