hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4557) Few issues in scheduling with Node Labels
Date Fri, 08 Jan 2016 17:19:39 GMT

     [ https://issues.apache.org/jira/browse/YARN-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Naganarasimha G R updated YARN-4557:
------------------------------------
    Attachment: YARN-4557.v2.002.patch

{{TestNodeLabelContainerAllocation}}  was failing because test case was not considering the
inheriting of the accessible node labels from parent and also added a new test case class
for {{PartitionedQueueComparator}},
[~wangda], can you take a look at this jira and the latest patch ?

> Few issues in scheduling with Node Labels
> -----------------------------------------
>
>                 Key: YARN-4557
>                 URL: https://issues.apache.org/jira/browse/YARN-4557
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Naganarasimha G R
>            Assignee: Naganarasimha G R
>            Priority: Minor
>         Attachments: YARN-4557.v1.001.patch, YARN-4557.v2.001.patch, YARN-4557.v2.002.patch
>
>
> * When app has submitted requests for multiple priority in default partition, then if
one of the priority requests has missed  non-partitioned-resource-request equivalent to cluster
size then container needs to be allocated. Currently if the higher priority requests doesn't
satisfy the condition, then whole application is getting skipped instead the priority
> * When queue has * as accessibility, then the queue ordering was not happening properly.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message