[
https://issues.apache.org/jira/browse/HADOOP-10893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105697#comment-14105697
]
Jason Lowe commented on HADOOP-10893:
-------------------------------------
Thanks for updating the branch-2 patch, Sangjin.
I noticed that in that patch hadoop.cmd doesn't have the same comments as were
added for the new env variables in the trunk patch. Could you update the
branch-2 patch to add that as well for consistency? Similarly there were
comments and a example exports added to hadoop-env.sh in the trunk patch that
are missing from the branch-2 patch. Not sure if the comments in
hadoop-config.sh should be moved/copied to hadoop-env.sh and sample exports
added or if we want them left in hadoop-config.sh for branch-2.
> 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)
