You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Benjamin Teke (Jira)" <ji...@apache.org> on 2021/11/12 16:38:00 UTC

[jira] [Created] (YARN-11006) Allow overriding user limit factor and maxAMResourcePercent with AQCv2 templates

Benjamin Teke created YARN-11006:
------------------------------------

             Summary: Allow overriding user limit factor and maxAMResourcePercent with AQCv2 templates
                 Key: YARN-11006
                 URL: https://issues.apache.org/jira/browse/YARN-11006
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Benjamin Teke
            Assignee: Benjamin Teke


[YARN-10801|https://issues.apache.org/jira/browse/YARN-10801] fixed the template configurations for every queue property, but it introduced a strange behaviour as well. When setting the template configurations LeafQueue.setDynamicQueueProperties is called:

{code:java}
  @Override
  protected void setDynamicQueueProperties(
      CapacitySchedulerConfiguration configuration) {
    super.setDynamicQueueProperties(configuration);
    // set to -1, to disable it
    configuration.setUserLimitFactor(getQueuePath(), -1);
    // Set Max AM percentage to a higher value
    configuration.setMaximumApplicationMasterResourcePerQueuePercent(
        getQueuePath(), 1f);
  }
{code}

This sets the configured template properties in the configuration object and then it overwrites the user limit factor and the maximum AM resource percent values with the hardcoded ones. The order should be reversed.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org