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-4887) AM-RM protocol changes for identifying resource-requests explicitly
Date Thu, 09 Jun 2016 20:13:21 GMT

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

Subru Krishnan updated YARN-4887:
    Attachment: YARN-4887-v5.patch

Rebased and addressed the feedback from [~leftnoteasy] and others captured [here|https://issues.apache.org/jira/browse/YARN-4879?focusedCommentId=15323233]

> AM-RM protocol changes for identifying resource-requests explicitly
> -------------------------------------------------------------------
>                 Key: YARN-4887
>                 URL: https://issues.apache.org/jira/browse/YARN-4887
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: applications, resourcemanager
>            Reporter: Subru Krishnan
>            Assignee: Subru Krishnan
>         Attachments: YARN-4887-v1.patch, YARN-4887-v2.patch, YARN-4887-v3.patch, YARN-4887-v4.patch,
> YARN-4879 proposes the notion of identifying allocate requests explicitly.. This JIRA
is to track the changes in AM-RM protocol to accomplish it. The crux is the addition of ID
field in ResourceRequest and Container. The detailed proposal can be referred in the parent

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