[
https://issues.apache.org/jira/browse/MAPREDUCE-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615365#comment-13615365
]
Abhishek Gayakwad commented on MAPREDUCE-5106:
----------------------------------------------
I am using 0.20.2 version, where config is loaded from job.xml
this.localJobFile = default_conf.getLocalPath(JobTracker.SUBDIR+"/"+jobId +
".xml");
conf = new JobConf(localJobFile);
I have tested this as well. It is okay to close this issue if it is fixed in
1.0.
> 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
