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

AM uses mapreduce.jobtracker.split.metainfo.maxsize but mapred-default has mapreduce.job.split.metainfo.maxsize

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.23.3, 2.0.2-alpha
    • 0.23.7, 2.1.0-beta
    • mrv2
    • None

    Description

      When the user needs to configure a larger split metainfo file size, mapred-default.xml points to the mapreduce.job.split.metainfo.maxsize property. However the ApplicationMaster actually uses the mapreduce.jobtracker.split.metainfo.maxsize property when determining the largest allowed size. This leads to much confusion on the part of end-users trying to increase the allowed limit.

      Attachments

        1. MAPREDUCE-4871.patch
          4 kB
          Jason Darrell Lowe

        Issue Links

          Activity

            People

              jlowe Jason Darrell Lowe
              jlowe Jason Darrell Lowe
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: