You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Subru Krishnan (JIRA)" <ji...@apache.org> on 2016/08/01 22:10:20 UTC
[jira] [Updated] (YARN-4888) Changes in RM container allocation for
identifying resource-requests explicitly
[ 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-v5.patch
Updating patch (v5) with new test {{TestAppSchedulingInfo::testSchedulerRequestKeyOrdering}} as requested by [~asuresh].
{{TestDirectoryCollection}} failure is unrelated to this patch.
> Changes in RM container allocation 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-v2.patch, YARN-4888-v3.patch, YARN-4888-v4.patch, YARN-4888-v5.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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org