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

references to JobConf.DISABLE_MEMORY_LIMIT don't make sense in the context of MR2

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • 2.0.4-alpha
    • None
    • None
    • None

    Description

      In MR1, a special value of -1 could be given for mapreduce.job.map|reduce.memory.mb when memory limits were disabled. In MR2, this makes no sense, as with slots gone, this value is used for requesting resources and scheduling.

      Attachments

        Issue Links

          Activity

            People

              sandyr Sandy Ryza
              sandyr Sandy Ryza
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: