FAQ
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: Minor
Fix For: 0.21.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.

Search Discussions

  • Amar Kamat (JIRA) at Feb 24, 2009 at 4:38 am
    [ https://issues.apache.org/jira/browse/HADOOP-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676183#action_12676183 ]

    Amar Kamat commented on HADOOP-5306:
    ------------------------------------

    Tasks that are running on the tracker that is lost move to KILLED_UNCLEAN state. In this state a task level cleanup attempt (with the same id) is launched on a different tracker. Once this (cleanup) attempt returns, the attempt is marked KILLED_CLEAN (i.e KILLED). Once the (cleanup) attempt returns, the jobtracker tries to kill the attempt using the old tracker (lost tracker's) information which got deleted and hence the port information goes missing. Actually the port information is of no use to the jobtracker as the tracker is lost. Hence we can ignore this case. HADOOP-4638 can take care of this.
    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: Minor
    Fix For: 0.21.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.
  • Hemanth Yamijala (JIRA) at Feb 24, 2009 at 11:48 am
    [ 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.
  • Hemanth Yamijala (JIRA) at Feb 24, 2009 at 11:48 am
    [ https://issues.apache.org/jira/browse/HADOOP-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Hemanth Yamijala reassigned HADOOP-5306:
    ----------------------------------------

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


    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.
  • Amar Kamat (JIRA) at Feb 24, 2009 at 1:26 pm
    [ https://issues.apache.org/jira/browse/HADOOP-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Amar Kamat updated HADOOP-5306:
    -------------------------------

    Attachment: HADOOP-5306-v1.0.patch

    Attaching a straight forward fix.
    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.
  • Amareshwari Sriramadasu (JIRA) at Feb 25, 2009 at 5:15 am
    [ https://issues.apache.org/jira/browse/HADOOP-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676506#action_12676506 ]

    Amareshwari Sriramadasu commented on HADOOP-5306:
    -------------------------------------------------

    +1 patch looks good.
    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.
  • 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-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.
  • Amar Kamat (JIRA) at Feb 25, 2009 at 1:13 pm
    [ https://issues.apache.org/jira/browse/HADOOP-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676642#action_12676642 ]

    Amar Kamat commented on HADOOP-5306:
    ------------------------------------

    ant test passes on my box.
    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.
  • Devaraj Das (JIRA) at Feb 26, 2009 at 11:15 am
    [ https://issues.apache.org/jira/browse/HADOOP-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Devaraj Das resolved HADOOP-5306.
    ---------------------------------

    Resolution: Fixed
    Hadoop Flags: [Reviewed]

    I just committed this. Thanks, Amar!
    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.
  • Hudson (JIRA) at Feb 26, 2009 at 3:14 pm
    [ 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.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedFeb 23, '09 at 8:45a
activeFeb 26, '09 at 3:14p
posts10
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Hudson (JIRA): 10 posts

People

Translate

site design / logo © 2022 Grokbase