[
https://issues.apache.org/jira/browse/YARN-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276156#comment-14276156
]
Yuliya Feldman commented on YARN-2791:
--------------------------------------
Thank you Vinod for your comment, as [~sdaingade] suggested in his previous
comment let's make this JIRA as subtask of [YARN-2139 |
https://issues.apache.org/jira/browse/YARN-2139 ] and do design discussion and
code walk through if necessary to determine whether it fits into existing
subtask or it will continue being it's own.
Yes we definitely understand you opened YARN-2139 first.
> 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
> Attachments: DiskDriveAsResourceInYARN.pdf
>
>
> 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)
