Craig Welch commented on YARN-2496:


I think there’s a bug in the way a user’s consumed value is obtained when 
working with labels (it’s unchanged from the existing behavior, but it needs to 
change, I think)  The consumed is going to be for all jobs regardless of lable 
regardless of label expression but it’s being subtracted from a value which is 
limited to the user expression, so - this could be incorrect if user has some 
jobs w/out labels and some with (or with different labels) in the same queue.  
Jobs using labels could be starved due to jobs running under the same user with 
other labels.  I believe consumed resources needs to be per label and/or label 

> [YARN-796] Changes for capacity scheduler to support allocate resource 
> respect labels
> -------------------------------------------------------------------------------------
>                 Key: YARN-2496
>                 URL: https://issues.apache.org/jira/browse/YARN-2496
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: YARN-2496.patch, YARN-2496.patch, YARN-2496.patch, 
> YARN-2496.patch
> This JIRA Includes:
> - Add/parse labels option to {{capacity-scheduler.xml}} similar to other 
> options of queue like capacity/maximum-capacity, etc.
> - Include a "default-label-expression" option in queue config, if an app 
> doesn't specify label-expression, "default-label-expression" of queue will be 
> used.
> - Check if labels can be accessed by the queue when submit an app with 
> labels-expression to queue or update ResourceRequest with label-expression
> - Check labels on NM when trying to allocate ResourceRequest on the NM with 
> label-expression
> - Respect  labels when calculate headroom/user-limit

This message was sent by Atlassian JIRA

Reply via email to