hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4888) Changes in RM AppSchedulingInfo for identifying resource-requests explicitly
Date Sun, 17 Jul 2016 04:28:20 GMT

    [ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381080#comment-15381080

Arun Suresh commented on YARN-4888:

bq. How easy/hard would it be to do this as two patches - one that switches the current code
to use SchedulerKey and another to add allocation_request_id?
It is pretty straightforward. Created YARN-5392, where we shall replace Priority with a SchedulerKey.
And once that is done, we can incorporate the *allocationRequestId* into the SchedulerKey.

> 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-WIP.patch, YARN-4888-v0.patch, YARN-4888.001.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