-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 0.23.3, 2.0.2-alpha
-
Fix Version/s: 0.23.7, 2.1.0-beta
-
Component/s: mrv2
-
Labels:None
-
Target Version/s:
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.
- relates to
-
MAPREDUCE-4926 Change documentation to use mapreduce.jobtracker.split.metainfo.maxsize
-
- Resolved
-
-
MAPREDUCE-2760 mapreduce.jobtracker.split.metainfo.maxsize typoed in mapred-default.xml
-
- Closed
-