hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4952) FSSchedulerNode is always instantiated with a 0 virtual core capacity
Date Mon, 21 Jan 2013 09:48:15 GMT

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

Harsh J commented on MAPREDUCE-4952:
------------------------------------

One may also use More Actions -> Move to move incorrect JIRAs to their right project, and
URLs are automatically mapped to the new one, making the process more elegant. Just something
for future :-)
                
> 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

Mime
View raw message