Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 13 Oct 2011 01:17:11 +0000 (UTC)
From: "Jonathan Eagles (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1072814156.7568.1318468631892.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1798068554.12358.1310157976821.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-2666) MR-279: Need to retrieve
 shuffle port number on ApplicationMaster restart
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Eagles commented on MAPREDUCE-2666:
--------------------------------------------

Thanks to Bobby, Vinod, and Arun for helping to get this in.

bq. I just committed this. Thanks Jonathan!
bq. Thanks to Bobby and Vinod for reviews.
                
> MR-279: Need to retrieve shuffle port number on ApplicationMaster restart
> -------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2666
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Robert Joseph Evans
>            Assignee: Jonathan Eagles
>            Priority: Blocker
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2666.patch, MAPREDUCE-2666.patch
>
>
> MAPREDUCE-2652 allows ShuffleHandler to return the port it is operating on.  In the case of an ApplicationMaster crash where it needs to be restarted that information is lost.  We either need to re-query it from each of the NodeManagers or to persist it to the JobHistory logs and retrieve it again.  The job history logs is probably the simpler solution.

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