[
https://issues.apache.org/jira/browse/YARN-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527792#comment-14527792
]
Karthik Kambatla commented on YARN-2618:
----------------------------------------
[~vinodkv] - we were thinking of working on a branch and merge back to trunk in
phases. Do you think this alone can directly go to trunk?
Related - it would be nice if the scheduler parts of YARN-2140 are also worked
on in a branch. Also, looking to hear thoughts on the branch-development thread
on yarn-dev@
> Avoid over-allocation of disk resources
> ---------------------------------------
>
> Key: YARN-2618
> URL: https://issues.apache.org/jira/browse/YARN-2618
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Wei Yan
> Assignee: Wei Yan
> Attachments: YARN-2618-1.patch, YARN-2618-2.patch, YARN-2618-3.patch,
> YARN-2618-4.patch, YARN-2618-5.patch, YARN-2618-6.patch, YARN-2618-7.patch
>
>
> Subtask of YARN-2139.
> This should include
> - Add API support for introducing disk I/O as the 3rd type resource.
> - NM should report this information to the RM
> - RM should consider this to avoid over-allocation
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
