hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4871) AM uses mapreduce.jobtracker.split.metainfo.maxsize but mapred-default has mapreduce.job.split.metainfo.maxsize
Date Fri, 01 Mar 2013 14:05:18 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590536#comment-13590536
] 

Hudson commented on MAPREDUCE-4871:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #1359 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1359/])
    MAPREDUCE-4871. AM uses mapreduce.jobtracker.split.metainfo.maxsize but mapred-default
has mapreduce.job.split.metainfo.maxsize (Jason Lowe via jeagles) (Revision 1451318)

     Result = SUCCESS
jeagles : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1451318
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRJobConfig.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/split/SplitMetaInfoReader.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/util/ConfigUtil.java

                
> 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: 0.23.3, 2.0.2-alpha
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>             Fix For: 3.0.0, 0.23.7, 2.0.4-beta
>
>         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