Andrey Stepachev commented on YARN-2134:

This is a first of two patches for deep hierarchical queues. For example in day 
or two I'll prepare patch which fixes situation with deep min share.
Code from test case, with current implementation of the scheduler queues will 
get fair share between queues {bit, sub1 and sub2} and will not take in account 
min share specified for sub1.sub11. 
I wan't to propogate min share for FSParentQueue from deeper levels. And in 
that case specified properties should work.
PrintWriter out = new PrintWriter(new FileWriter(ALLOC_FILE));
    out.println("<?xml version=\"1.0\"?>");
    out.println("<queue name=\"queue1\">");
    out.println("  <maxResources>10240mb, 10vcores</maxResources>");
    out.println("  <queue name=\"big\"/>");
    out.println("  <queue name=\"sub1\">");
    out.println("    <schedulingPolicy>fair</schedulingPolicy>");
    out.println("    <queue name=\"sub11\">");
    out.println("      <minResources>6192mb, 6vcores</minResources>");
    out.println("    </queue>");
    out.println("  </queue>");
    out.println("  <queue name=\"sub2\">");
    out.println("  </queue>");

> FairSchduler AllocationConfiguration doesn't treat hierarchical queues 
> settings
> -------------------------------------------------------------------------------
>                 Key: YARN-2134
>                 URL: https://issues.apache.org/jira/browse/YARN-2134
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 2.5.0
>            Reporter: Andrey Stepachev
>         Attachments: YARN-2134-v2.diff, YARN-2134.diff
> Automatically created queues (f.e. by queue placement rules) doesn't allow to 
> set default parameters. If queue not configured explicitly, queue parameters 
> will be set from global defaults. This patch allows to use parent queue 
> parameters.

This message was sent by Atlassian JIRA

Reply via email to