[
https://issues.apache.org/jira/browse/MAPREDUCE-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved MAPREDUCE-5106.
--------------------------------
Resolution: Not A Problem
Looking at branch-1's implementation (JobInProgress), this is not a current
problem. Resolving as Not a Problem. The config is taken from the
JobTracker.getConf() call so the two cannot be mixed as reported.
What version were you using?
> mapreduce.jobtracker.split.metainfo.maxsize can be set at job level
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-5106
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5106
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.20.2
> Reporter: Abhishek Gayakwad
> Priority: Minor
>
> mapreduce.jobtracker.split.metainfo.maxsize gives an impression that this
> property can be set at JT level only and will require JT restart in case of
> any modification. But actually this can be set at individual job level.
> So either this property should be named properly or should be restricted to
> JT level only.
--
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
