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 "Wangda Tan (JIRA)" <ji...@apache.org> on 2016/08/05 17:42:20 UTC
[jira] [Updated] (YARN-4888) Changes in scheduler to identify
resource-requests explicitly by allocation-id
[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wangda Tan updated YARN-4888:
-----------------------------
Summary: Changes in scheduler to identify resource-requests explicitly by allocation-id (was: Changes in RM container allocation for identifying resource-requests explicitly)
> Changes in scheduler to identify resource-requests explicitly by allocation-id
> ------------------------------------------------------------------------------
>
> 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-v6.patch, YARN-4888-v7.patch, YARN-4888-v8.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