Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-4584 Umbrella: Preemption and restart of MapReduce tasks
  3. MAPREDUCE-5848

MapReduce counts forcibly preempted containers as FAILED

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • 2.1.0-beta
    • None
    • None
    • None

    Description

      The MapReduce AM is considering a forcibly preempted container as FAILED, while I think it should be considered as KILLED (i.e., not count against the maximum number of failures).

      Attachments

        1. MR-5848.patch
          17 kB
          Subramaniam Krishnan
        2. MR-5848.patch
          2 kB
          Subramaniam Krishnan
        3. YARN-1958.patch
          1 kB
          Carlo Curino

        Issue Links

          relates to

          Sub-task - The sub-task of the issue MAPREDUCE-5900 Container preemption interpreted as task failures and eventually job failures

          • Major - Major loss of function.
          • Closed

          Activity

            People

              subru Subramaniam Krishnan
              curino Carlo Curino
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: