[
https://issues.apache.org/jira/browse/YARN-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200829#comment-14200829
]
Karthik Kambatla commented on YARN-2791:
----------------------------------------
[~adityakishore] - from reading the description, I believe there is at least a
significant overlap between the two JIRAs. I think we would benefit from
consolidating them and working together, than take multiple paths.
[~sdaingade] - nice to know you have something working. Could you look through
the design doc on YARN-2139 so we can refine it. If it is significantly
different from what is posted there, can you also post your design so we can
evaluate which one is better and move forward.
> Add Disk as a resource for scheduling
> -------------------------------------
>
> Key: YARN-2791
> URL: https://issues.apache.org/jira/browse/YARN-2791
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: scheduler
> Affects Versions: 2.5.1
> Reporter: Swapnil Daingade
> Assignee: Yuliya Feldman
>
> Currently, the number of disks present on a node is not considered a factor
> while scheduling containers on that node. Having large amount of memory on a
> node can lead to high number of containers being launched on that node, all
> of which compete for I/O bandwidth. This multiplexing of I/O across
> containers can lead to slower overall progress and sub-optimal resource
> utilization as containers starved for I/O bandwidth hold on to other
> resources like cpu and memory. This problem can be solved by considering disk
> as a resource and including it in deciding how many containers can be
> concurrently run on a node.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
