-
Notifications
You must be signed in to change notification settings - Fork 9.1k
YARN-10869. CS considers only the default maximum-allocation-mb/vcore property as a maximum when it creates dynamic queues #3225
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
… property as a maximum when it creates dynamic queues
🎊 +1 overall
This message was automatically generated. |
Thank you for the patch @bteke. This is a subtle issue, good finding! One note: |
@9uapaw thanks for checking this. I can think of one thing against populating the csContext config: if someone uses a large number of dynamically created queues (like user based ones with a large pool, or application name based dynamic queues, etc) the original configuration object could become pretty large, so some kind of property removal logic could be introduced. |
Thanks @brumi1024 for working on this. The code change looks good to me, committed to trunk. |
… property as a maximum when it creates dynamic queues (apache#3225) Co-authored-by: Benjamin Teke <bteke@cloudera.com>
… property as a maximum when it creates dynamic queues (apache#3225) Co-authored-by: Benjamin Teke <bteke@cloudera.com>
…ion-mb/vcore property as a maximum when it creates dynamic queues (apache#3225) Co-authored-by: Benjamin Teke <bteke@cloudera.com> (cherry picked from commit ac0a4e7) Change-Id: Ia8bfcf0694dc707ba5a5dabf042f30540da14084
… property as a maximum when it creates dynamic queues
NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute