You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Sandy Ryza (JIRA)" <ji...@apache.org> on 2013/01/21 04:06:13 UTC
[jira] [Updated] (MAPREDUCE-4952) FSSchedulerNode is always
instantiated with a 0 virtual core capacity
[ https://issues.apache.org/jira/browse/MAPREDUCE-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandy Ryza updated MAPREDUCE-4952:
----------------------------------
Component/s: scheduler
> FSSchedulerNode is always instantiated with a 0 virtual core capacity
> ---------------------------------------------------------------------
>
> Key: MAPREDUCE-4952
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4952
> Project: Hadoop Map/Reduce
> 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