[ https://issues.apache.org/jira/browse/HADOOP-10893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105830#comment-14105830 ]
Jason Lowe commented on HADOOP-10893: ------------------------------------- Sounds good, thanks for the clarification Sangjin and Allen! +1 for the latest patches, will commit this in a bit. > isolated classloader on the client side > --------------------------------------- > > Key: HADOOP-10893 > URL: https://issues.apache.org/jira/browse/HADOOP-10893 > Project: Hadoop Common > Issue Type: New Feature > Components: util > Affects Versions: 2.4.0 > Reporter: Sangjin Lee > Assignee: Sangjin Lee > Attachments: HADOOP-10893-branch-2.patch, > HADOOP-10893-branch-2.patch, HADOOP-10893.patch, HADOOP-10893.patch, > HADOOP-10893.patch, HADOOP-10893.patch, HADOOP-10893.patch, > HADOOP-10893.patch, HADOOP-10893.patch, classloader-test.tar.gz > > > We have the job classloader on the mapreduce tasks that run on the cluster. > It has a benefit of being able to isolate class space for user code and avoid > version clashes. > Although it occurs less often, version clashes do occur on the client JVM. It > would be good to introduce an isolated classloader on the client side as well > to address this. A natural point to introduce this may be through RunJar, as > that's how most of hadoop jobs are run. -- This message was sent by Atlassian JIRA (v6.2#6252)