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 "Jason Lowe (Assigned) (JIRA)" <ji...@apache.org> on 2011/12/21 18:09:30 UTC
[jira] [Assigned] (MAPREDUCE-3271) Lost nodes list and count not
updated
[ https://issues.apache.org/jira/browse/MAPREDUCE-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Lowe reassigned MAPREDUCE-3271:
-------------------------------------
Assignee: Jason Lowe
> Lost nodes list and count not updated
> -------------------------------------
>
> Key: MAPREDUCE-3271
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3271
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ramya Sunil
> Assignee: Jason Lowe
> Priority: Critical
> Fix For: 0.23.1
>
>
> When nodemanagers are lost, the "Lost Nodes" list and the count is not incremented. Either we,
> 1. Fix the lost nodes list when a nodemanager is lost - The problem with tracking lost nodes is, if the nodemanager joins back, there would be duplicate entries in active and lost nodes with different port numbers.
> 2. Do not track lost nodemanagers
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira