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 "Wei Yan (JIRA)" <ji...@apache.org> on 2014/10/31 22:35:35 UTC
[jira] [Commented] (YARN-2791) Add Disk as a resource for
scheduling
[ https://issues.apache.org/jira/browse/YARN-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192536#comment-14192536 ]
Wei Yan commented on YARN-2791:
-------------------------------
Hi, [~sdaingade]. Is this a duplicate of YARN-2139? We have worked on the disk I/O scheduling for a while, and will post patches soon after more experiments.
> 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
>
> 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)