Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major 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.
    1. MAPREDUCE-677-v1.0.patch
      0.8 kB
      Amar Kamat
    2. MAPREDUCE-677-v1.1.patch
      0.9 kB
      Amar Kamat
    3. MAPREDUCE-677-v1.1-branch-0.20.patch
      1.0 kB
      Amar Kamat
    4. TEST-org.apache.hadoop.mapred.TestNodeRefresh.txt
      335 kB
      Jothi Padmanabhan

      Activity

      Amar Kamat created issue -
      Amar Kamat made changes -
      Field Original Value New Value
      Attachment MAPREDUCE-677-v1.0.patch [ 12412836 ]
      Amar Kamat made changes -
      Attachment MAPREDUCE-677-v1.1.patch [ 12412995 ]
      Sharad Agarwal made changes -
      Status Open [ 1 ] Resolved [ 5 ]
      Hadoop Flags [Reviewed]
      Fix Version/s 0.21.0 [ 12314045 ]
      Resolution Fixed [ 1 ]
      Amar Kamat made changes -
      Attachment MAPREDUCE-677-v1.1-branch-0.20.patch [ 12413086 ]
      Amar Kamat made changes -
      Release Note 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.
      Jothi Padmanabhan made changes -
      Resolution Fixed [ 1 ]
      Status Resolved [ 5 ] Reopened [ 4 ]
      Jothi Padmanabhan made changes -
      Amar Kamat made changes -
      Status Reopened [ 4 ] Resolved [ 5 ]
      Resolution Fixed [ 1 ]
      Tom White made changes -
      Status Resolved [ 5 ] Closed [ 6 ]

        People

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

          Dates

          • Created:
            Updated:
            Resolved:

            Development