Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Wed, 21 Dec 2011 17:09:30 +0000 (UTC)
From: "Jason Lowe (Assigned) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <2054378826.36047.1324487370792.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <666959113.15800.1319585552219.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (MAPREDUCE-3271) Lost nodes list and count not
 updated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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