hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1631) Container allocation issue in Leafqueue assignContainers()
Date Wed, 29 Jan 2014 11:06:09 GMT

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

Sunil G updated YARN-1631:
--------------------------

    Attachment: Yarn-1631.2.patch

Updated with test case to reproduce this scenario.
Please review the same.

> Container allocation issue in Leafqueue assignContainers()
> ----------------------------------------------------------
>
>                 Key: YARN-1631
>                 URL: https://issues.apache.org/jira/browse/YARN-1631
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 2.2.0
>         Environment: SuSe 11 Linux 
>            Reporter: Sunil G
>         Attachments: Yarn-1631.1.patch, Yarn-1631.2.patch
>
>
> Application1 has a demand of 8GB[Map Task Size as 8GB] which is more than Node_1 can
handle.
> Node_1 has a size of 8GB and 2GB is used by Application1's AM.
> Hence reservation happened for remaining 6GB in Node_1 by Application1.
> A new job is submitted with 2GB AM size and 2GB task size with only 2 Maps to run.
> Node_2 also has 8GB capability.
> But Application2's AM cannot be launched in Node_2. And Application2 waits longer as
only 2 Nodes are available in cluster.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message