 |
Amar Kamat (JIRA) |
at Feb 25, 2009 at 6:23 am
|
⇧ | 
| |
[
https://issues.apache.org/jira/browse/HADOOP-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676524#action_12676524 ]
Amar Kamat commented on HADOOP-5306:
------------------------------------
Test-patch result
{code}
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new or modified tests.
[exec] Please justify why no tests are needed for this patch.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
[exec]
[exec] +1 release audit. The applied patch does not increase the total number of release audit warnings.
{code}
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-5306Project: 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.
