[
https://issues.apache.org/jira/browse/MAPREDUCE-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753994#action_12753994
]
Todd Lipcon commented on MAPREDUCE-967:
---------------------------------------
bq. Now that there are changes to RunJar, for trunk, can you move RunJar to
mapreduce from common
Sure thing. I'll take care of that when I post the patch for trunk.
bq. Also, I think, it will be good to make the filter to specify the
directories/files in job.jar to be un-jarred as configurable
Do you see any use for filters here beyond a straight regex? We can express the
old behaviour as /.*/ and the new behavior as /^(lib|classes)\//. Also, I'd
prefer to make this an *undocumented* configuration parameter, since I think
there is very little use for the old version and we don't want to encourage
people to abuse this.
Would you see this being used as a per-job option or a TaskTracker-scoped
option?
> TaskTracker does not need to fully unjar job jars
> -------------------------------------------------
>
> Key: MAPREDUCE-967
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-967
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: tasktracker
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: mapreduce-967-branch-0.20.txt
>
>
> In practice we have seen some users submitting job jars that consist of
> 10,000+ classes. Unpacking these jars into mapred.local.dir and then cleaning
> up after them has a significant cost (both in wall clock and in unnecessary
> heavy disk utilization). This cost can be easily avoided
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
