[
https://issues.apache.org/jira/browse/HADOOP-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677023#action_12677023
]
Hudson commented on HADOOP-5306:
--------------------------------
Integrated in Hadoop-trunk #766 (See
[http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/766/])
. Fixes a problem to do with logging/parsing the http port of a lost
tracker. Affects JobTracker restart. Contributed by Amar Kamat.
> Job History file can have empty string as http port after JobTracker Restart
> in case of lost TT, which can result in NumberFormatException when JT is
> restarted 2nd time
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5306
> URL: https://issues.apache.org/jira/browse/HADOOP-5306
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Ravi Gummadi
> Assignee: Amar Kamat
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HADOOP-5306-v1.0.patch
>
>
> HTTP_PORT="" is seen in job history file after JT recovery in case of lost
> TT. The .recover file of TestJobTrackerRestartWithLostTracker has empty
> string as HTTP_PORT. If another time JT is restarted and then JT tries to
> read the history line and tries to createTaskAttempt, it would get
> NumberFormatException because of Integer.parseInt(httpPort). We somehow need
> to log a legal value as HTTP_PORT in the history file OR the exception needs
> to be caught and proper action is to be taken.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
