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 "Sandy Ryza (JIRA)" <ji...@apache.org> on 2013/05/14 23:07:16 UTC

[jira] [Resolved] (YARN-350) FSSchedulerNode is always instantiated with a 0 virtual core capacity

     [ https://issues.apache.org/jira/browse/YARN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sandy Ryza resolved YARN-350.
-----------------------------

    Resolution: Duplicate
    
> FSSchedulerNode is always instantiated with a 0 virtual core capacity
> ---------------------------------------------------------------------
>
>                 Key: YARN-350
>                 URL: https://issues.apache.org/jira/browse/YARN-350
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 2.0.2-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>
> After YARN-2, FSSchedulerNode was not updated to initialize with the underlying RMNode's CPU capacity, and thus always has 0 virtual cores.

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