[
https://issues.apache.org/jira/browse/MAPREDUCE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838320#comment-13838320
]
Hitesh Shah commented on MAPREDUCE-5487:
----------------------------------------
A little bit late on this. Did anyone look into how this affects jobs where a
user modifies the counter limit to be higher than the cluster configured value
and what happens in the case where the jobhistory server is configured with a
limit less than the user supplied limit?
> In task processes, JobConf is unnecessarily loaded again in Limits
> ------------------------------------------------------------------
>
> Key: MAPREDUCE-5487
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5487
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance, task
> Affects Versions: 2.1.0-beta
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Fix For: 2.4.0
>
> Attachments: MAPREDUCE-5487-1.patch, MAPREDUCE-5487.patch
>
>
> Limits statically loads a JobConf, which incurs costs of reading files from
> disk and parsing XML. The contents of this JobConf are identical to the one
> loaded by YarnChild (before adding job.xml as a resource). Allowing Limits
> to initialize with the JobConf loaded in YarnChild would reduce task startup
> time.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
