hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4871) AM uses mapreduce.jobtracker.split.metainfo.maxsize but mapred-default has mapreduce.job.split.metainfo.maxsize
Date Tue, 08 Jan 2013 22:06:13 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Lowe updated MAPREDUCE-4871:
----------------------------------

    Target Version/s: 2.0.3-alpha, 0.23.6
              Status: Patch Available  (was: Open)
    
> 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
>            Assignee: Jason Lowe
>         Attachments: MAPREDUCE-4871.patch
>
>
> 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

Mime
View raw message