Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.21.0
    • Component/s: test
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Hide
      TestNodeRefresh sometimes timed out. This happened because the test started a MR cluster with 2 trackers and ran a half-waiting-mapper job. Tasks that have id > total-maps/2 wait for a signal. Because of 2 trackers, the tasks got scheduled out of order (locality) and hence the job got stuck. The fix is to start only one tracker and then add a new tracker later.
      Show
      TestNodeRefresh sometimes timed out. This happened because the test started a MR cluster with 2 trackers and ran a half-waiting-mapper job. Tasks that have id > total-maps/2 wait for a signal. Because of 2 trackers, the tasks got scheduled out of order (locality) and hence the job got stuck. The fix is to start only one tracker and then add a new tracker later.

      Attachments

      1. TEST-org.apache.hadoop.mapred.TestNodeRefresh.txt
        335 kB
        Jothi Padmanabhan
      2. MAPREDUCE-677-v1.1-branch-0.20.patch
        1.0 kB
        Amar Kamat
      3. MAPREDUCE-677-v1.1.patch
        0.9 kB
        Amar Kamat
      4. MAPREDUCE-677-v1.0.patch
        0.8 kB
        Amar Kamat

        Activity

          People

          • Assignee:
            amar_kamat Amar Kamat
            Reporter:
            amar_kamat Amar Kamat
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: