hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Subru Krishnan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4888) Changes in RM AppSchedulingInfo for identifying resource-requests explicitly
Date Sat, 09 Jul 2016 01:16:10 GMT

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

Subru Krishnan updated YARN-4888:
    Attachment: YARN-4888-v0.patch

I am uploading a WIP patch as the change is pretty involved. This patch adds an _allocationRequestId_
key in {{AppSchedulingInfo.resourceRequestMap}} and maps the allocated container against the
_ResourceRequest_ which it satisfies.

I have got the existing test cases for _Capacity/Fair/Fifo_ schedulers working *except* for
the ones related to node labels. I am looking into those, meanwhile it would be good to review
the patch to make sure the approach I have taken is sound as the changes affect core parts
of RM.
I also need to add tests with _ResourceRequest_ that use the new _allocationRequestId_ feature.

> Changes in RM AppSchedulingInfo for identifying resource-requests explicitly
> ----------------------------------------------------------------------------
>                 Key: YARN-4888
>                 URL: https://issues.apache.org/jira/browse/YARN-4888
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Subru Krishnan
>            Assignee: Subru Krishnan
>         Attachments: YARN-4888-v0.patch
> YARN-4879 puts forward the notion of identifying allocate requests explicitly. This JIRA
is to track the changes in RM app scheduling data structures to accomplish it. Please refer
to the design doc in the parent JIRA for details.

This message was sent by Atlassian JIRA

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

View raw message