[jira] [Created] (YARN-11059) Investigate whether legacy Auto Queue Creation in absolute mode works seamlessly when calling updateClusterResource

["Andras Gyori (Jira)" <ji...@apache.org>]

Andras Gyori created YARN-11059:
-----------------------------------

             Summary: Investigate whether legacy Auto Queue Creation in absolute mode works seamlessly when calling updateClusterResource
                 Key: YARN-11059
                 URL: https://issues.apache.org/jira/browse/YARN-11059
             Project: Hadoop YARN
          Issue Type: Bug
          Components: yarn
            Reporter: Andras Gyori
            Assignee: Andras Gyori


Due to this check in ParentQueue#getCapacityConfigurationTypeForQueues:
{code:java}
if (queues.iterator().hasNext() &&
    !queues.iterator().next().getQueuePath().equals(
    CapacitySchedulerConfiguration.ROOT) &&
    (percentageIsSet ? 1 : 0) + (weightIsSet ? 1 : 0) + (absoluteMinResSet ?
        1 :
        0) > 1) {
  throw new IOException("Parent queue '" + getQueuePath()
      + "' have children queue used mixed of "
      + " weight mode, percentage and absolute mode, it is not allowed, please "
      + "double check, details:" + diagMsg.toString());
} {code}
I was unable to call updateClusterResource on a ManagedParentQueue, when its children are in absolute mode. updateClusterResource is called whenever a node is updated etc., therefore it could break any time.



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

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