[jira] Updated: (HADOOP-5306) 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

["Hemanth Yamijala (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hemanth Yamijala updated HADOOP-5306:
-------------------------------------

         Priority: Blocker  (was: Minor)
    Fix Version/s:     (was: 0.21.0)
                   0.20.0

Marking this for 0.20 as a blocker. Because this will cause the recovery to completely fail the job tracker.

> 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
>            Priority: Blocker
>             Fix For: 0.20.0
>
>
> 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.