Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-2324

Job should fail if a reduce task can't be scheduled anywhere

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.20.2, 0.20.205.0
    • Fix Version/s: 0.20.205.0
    • Component/s: None
    • Labels:
      None

      Description

      If there's a reduce task that needs more disk space than is available on any mapred.local.dir in the cluster, that task will stay pending forever. For example, we produced this in a QA cluster by accidentally running terasort with one reducer - since no mapred.local.dir had 1T free, the job remained in pending state for several days. The reason for the "stuck" task wasn't clear from a user perspective until we looked at the JT logs.

      Probably better to just fail the job if a reduce task goes through all TTs and finds that there isn't enough space.

        Attachments

        1. MR-2324-security-v1.txt
          9 kB
          Robert Joseph Evans
        2. MR-2324-security-v2.txt
          9 kB
          Robert Joseph Evans
        3. MR-2324-security-v3.patch
          10 kB
          Robert Joseph Evans
        4. MR-2324-secutiry-just-log-v1.patch
          0.7 kB
          Robert Joseph Evans
        5. MR-2324-disable-check-v2.patch
          0.9 kB
          Robert Joseph Evans

          Activity

            People

            • Assignee:
              revans2 Robert Joseph Evans
              Reporter:
              tlipcon Todd Lipcon
            • Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: