-
Notifications
You must be signed in to change notification settings - Fork 9.2k
YARN-11081. TestYarnConfigurationFields consistently keeps failing #4027
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
|
🎊 +1 overall
This message was automatically generated. |
aajisaka
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.
I think we should document the parameter in yarn-default.xml.
|
Thanks @aajisaka. Based on the ApplicationPlacementAllocatorFactory, it looks like the code has sufficient null check to handle missing property value: Moreover, I just checked latest 5-6 configs that are added to |
|
The unit test is to guarantee that all the YARN parameter is documented in yarn-default.xml. We should not add any parameter to configurationPrefixToSkipCompare without some specific reason (e.g., deprecated parameter). |
I see, the configs that I saw were deprecated ones. Thanks for the info. Addressed the comment in the latest commit. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
aajisaka
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.
+1. Thank you @virajjasani
…pache#4027) Signed-off-by: Akira Ajisaka <aajisaka@apache.org>
Description of PR
TestYarnConfigurationFields consistently keeps failing:
How was this patch tested?
Locally
For code changes: