Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.21.0
    • Component/s: jobtracker
    • Labels:
      None
    • Release Note:
      TestNodeRefresh timed out as the code to do with node refresh got removed. This patch removes the testcase.

      Activity

      Hide
      Konstantin Boudnik added a comment -

      It seems to be caused the unhandled crash in MiniMRCluster.startTaskTracker

           [exec]     [junit] 2009-08-31 11:59:24,583 INFO  mapred.TaskTracker (TaskTracker.java:initialize(567)) - TaskTracker up at: localhost/127.0.0.1:45234
           [exec]     [junit] 2009-08-31 11:59:24,583 INFO  mapred.TaskTracker (TaskTracker.java:initialize(570)) - Starting tracker tracker_host2.com:localhost/127.0.0.1:45234
           [exec]     [junit] 2009-08-31 11:59:24,584 ERROR mapred.MiniMRCluster (MiniMRCluster.java:<init>(194)) - task tracker 2 crashed
           [exec]     [junit] java.io.IOException: Call to localhost/127.0.0.1:47063 failed on local exception: java.io.EOFException
           [exec]     [junit] 	at org.apache.hadoop.ipc.Client.wrapException(Client.java:801)
           [exec]     [junit] 	at org.apache.hadoop.ipc.Client.call(Client.java:769)
      ...
           [exec]     [junit] 	at org.apache.hadoop.mapred.MiniMRCluster$TaskTrackerRunner.<init>(MiniMRCluster.java:189)
           [exec]     [junit] 	at org.apache.hadoop.mapred.MiniMRCluster.startTaskTracker(MiniMRCluster.java:675)
           [exec]     [junit] 	at org.apache.hadoop.mapred.TestNodeRefresh.testMRExcludeHostsAcrossRestarts(TestNodeRefresh.java:455)
      
      Show
      Konstantin Boudnik added a comment - It seems to be caused the unhandled crash in MiniMRCluster.startTaskTracker [exec] [junit] 2009-08-31 11:59:24,583 INFO mapred.TaskTracker (TaskTracker.java:initialize(567)) - TaskTracker up at: localhost/127.0.0.1:45234 [exec] [junit] 2009-08-31 11:59:24,583 INFO mapred.TaskTracker (TaskTracker.java:initialize(570)) - Starting tracker tracker_host2.com:localhost/127.0.0.1:45234 [exec] [junit] 2009-08-31 11:59:24,584 ERROR mapred.MiniMRCluster (MiniMRCluster.java:<init>(194)) - task tracker 2 crashed [exec] [junit] java.io.IOException: Call to localhost/127.0.0.1:47063 failed on local exception: java.io.EOFException [exec] [junit] at org.apache.hadoop.ipc.Client.wrapException(Client.java:801) [exec] [junit] at org.apache.hadoop.ipc.Client.call(Client.java:769) ... [exec] [junit] at org.apache.hadoop.mapred.MiniMRCluster$TaskTrackerRunner.<init>(MiniMRCluster.java:189) [exec] [junit] at org.apache.hadoop.mapred.MiniMRCluster.startTaskTracker(MiniMRCluster.java:675) [exec] [junit] at org.apache.hadoop.mapred.TestNodeRefresh.testMRExcludeHostsAcrossRestarts(TestNodeRefresh.java:455)
      Hide
      Amar Kamat added a comment -

      Can someone upload the log file?

      Show
      Amar Kamat added a comment - Can someone upload the log file?
      Hide
      Amar Kamat added a comment -

      Post MAPREDUCE-873, TestNodeRefresh.testMRExcludeHostsAcrossRestarts() will no longer be required. I dont think we should invest time in debugging this.

      Show
      Amar Kamat added a comment - Post MAPREDUCE-873 , TestNodeRefresh.testMRExcludeHostsAcrossRestarts() will no longer be required. I dont think we should invest time in debugging this.
      Hide
      Amar Kamat added a comment -

      Attaching a patch that removed the testcase.

      Show
      Amar Kamat added a comment - Attaching a patch that removed the testcase.
      Hide
      Amar Kamat added a comment -

      @Konstantin Yes the testcase got stuck because JobClient.startTracker() failed.

      Show
      Amar Kamat added a comment - @Konstantin Yes the testcase got stuck because JobClient.startTracker() failed.
      Hide
      Konstantin Boudnik added a comment -

      So, removing the test case seems to be the only way of 'fixing' the problem?

      Show
      Konstantin Boudnik added a comment - So, removing the test case seems to be the only way of 'fixing' the problem?
      Hide
      Konstantin Boudnik added a comment -

      If the cause of timeouts is connected to the MAPREDUCE-873 then this JIRA has to be converted to its sub-task. Otherwise, it seems to be confusing at first.

      Show
      Konstantin Boudnik added a comment - If the cause of timeouts is connected to the MAPREDUCE-873 then this JIRA has to be converted to its sub-task. Otherwise, it seems to be confusing at first.
      Hide
      Devaraj Das added a comment -

      I just committed this. Thanks, Amar!

      Show
      Devaraj Das added a comment - I just committed this. Thanks, Amar!
      Hide
      Devaraj Das added a comment -

      Should have added that I also agree that the testcase which times out is no longer needed.

      Show
      Devaraj Das added a comment - Should have added that I also agree that the testcase which times out is no longer needed.
      Hide
      Hudson added a comment -

      Integrated in Hadoop-Mapreduce-trunk-Commit #18 (See http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/18/)
      . Removes a testcase in TestNodeRefresh that doesn't make sense in the new Job recovery model. Contributed by Amar Kamat.

      Show
      Hudson added a comment - Integrated in Hadoop-Mapreduce-trunk-Commit #18 (See http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/18/ ) . Removes a testcase in TestNodeRefresh that doesn't make sense in the new Job recovery model. Contributed by Amar Kamat.

        People

        • Assignee:
          Amar Kamat
          Reporter:
          Amareshwari Sriramadasu
        • Votes:
          0 Vote for this issue
          Watchers:
          2 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development