hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2791) Add Disk as a resource for scheduling
Date Thu, 06 Nov 2014 22:44:34 GMT

    [ https://issues.apache.org/jira/browse/YARN-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201101#comment-14201101
] 

Karthik Kambatla commented on YARN-2791:
----------------------------------------

[~adityakishore] - unfortunately, YARN-2139 didn't have a description this far. I just added
a very succinct one. If you look at the design doc itself and the sub-tasks created, you would
see that YARN-2139 includes adding disk as a resource to the resource-request-vector, the
node-capacities, and the scheduler. 

[~sdaingade] - looking forward to you hear your thoughts and see a design doc.

> 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)

Mime
View raw message