[
https://issues.apache.org/jira/browse/HADOOP-10893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105819#comment-14105819
]
Allen Wittenauer commented on HADOOP-10893:
-------------------------------------------
tl;dr: [~sjlee0]'s changes here are probably the correct ones.
>From a pure patch perspective, it does look weird. But from a stylistic
>perspective as a part of a total work (namely, hadoop 2.x), the changes and
>lack of documentation in hadoop-env.sh, etc, to branch-2 make a lot of sense.
>One of the key points of HADOOP-9902 was to highlight to end users what things
>they could set. Hiding that in hadoop-config.sh, which users are never
>directed to documentation-wise, didn't really work. So I pulled those out and
>popped them into hadoop-env.sh, which users definitely see.
This change just got caught in the crossfire.
> 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)
