You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Sangjin Lee (JIRA)" <ji...@apache.org> on 2014/07/24 01:08:38 UTC

[jira] [Created] (HADOOP-10893) isolated classloader on the client side

Sangjin Lee created HADOOP-10893:
------------------------------------

             Summary: isolated classloader on the client side
                 Key: HADOOP-10893
                 URL: https://issues.apache.org/jira/browse/HADOOP-10893
             Project: Hadoop Common
          Issue Type: Bug
          Components: util
    Affects Versions: 2.4.0
            Reporter: Sangjin Lee
            Assignee: Sangjin Lee


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)