[jira] [Created] (MAPREDUCE-4871) AM uses mapreduce.jobtracker.split.metainfo.maxsize but mapred-default has mapreduce.job.split.metainfo.maxsize

["Jason Lowe (JIRA)" <ji...@apache.org>]

Jason Lowe created MAPREDUCE-4871:
-------------------------------------

             Summary: AM uses mapreduce.jobtracker.split.metainfo.maxsize but mapred-default has mapreduce.job.split.metainfo.maxsize
                 Key: MAPREDUCE-4871
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4871
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: mrv2
    Affects Versions: 2.0.2-alpha, 0.23.3
            Reporter: Jason Lowe


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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira