[ 
https://issues.apache.org/jira/browse/MAPREDUCE-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758987#action_12758987
 ] 

Vinod K V commented on MAPREDUCE-967:
-------------------------------------

Following the way we did this elsewhere (MAPREDUCE-711), we should
 - remove the old class _org.apache.hadoop.util.RunJar_ completely from the 
common project,
 - move the code completely to a new class 
_org.apache.hadoop.mapreduce.util.RunJar_ in mapreduce project
 - for supporting deprecation, create a new class in 
_org.apache.hadoop.util.RunJar_ in mapreduce project which is just a 
placeholder and redirects all the functionality to the class in 
_org.apache.hadoop.mapreduce.util.RunJar_. This class should be deprecated 
rightaway.
 - change all the framework references now to use 
_org.apache.hadoop.mapreduce.util.RunJar_

This avoids the cyclic dependency that you've mentioned. But it definitely 
breaks code of those who depend explicitly only on the common jar, but as 
discussed on MAPREDUCE-711 and in particular 
(https://issues.apache.org/jira/browse/MAPREDUCE-711?focusedCommentId=12729692&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12729692),
 project split already broke that kinda dependency.

> 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.

Reply via email to