Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 6 Nov 2014 19:34:34 +0000 (UTC)
From: "Wei Yan (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12752082.1414790667000.436841.1415302474973@Atlassian.JIRA>
In-Reply-To: <JIRA.12752082.1414790667000@Atlassian.JIRA>
References: <JIRA.12752082.1414790667000@Atlassian.JIRA>
 <JIRA.12752082.1414790667307@arcas>
Subject: [jira] [Commented] (YARN-2791) Add Disk as a resource for
 scheduling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Wei Yan commented on YARN-2791:
-------------------------------

Hi, [~yufeldman], this jira is same to YARN-2139.

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