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 "Bikas Saha (JIRA)" <ji...@apache.org> on 2012/12/25 00:18:12 UTC
[jira] [Commented] (YARN-289) Fair scheduler doesn't satisfy
smaller request when bigger one is outstanding
[ https://issues.apache.org/jira/browse/YARN-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539339#comment-13539339 ]
Bikas Saha commented on YARN-289:
---------------------------------
Could it be that 2048 request got "reserved" onto that node and that prevented the 1024 request from being assigned to that node?
> Fair scheduler doesn't satisfy smaller request when bigger one is outstanding
> ------------------------------------------------------------------------------
>
> Key: YARN-289
> URL: https://issues.apache.org/jira/browse/YARN-289
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
>
> An application requests a container with 1024 MB. It then requests a container with 2048 MB. A node shows up with 1024 MB available. Even if the application is the only one running, neither request will be scheduled on it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira