hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10893) isolated classloader on the client side
Date Thu, 21 Aug 2014 21:42:11 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-10893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Lowe updated HADOOP-10893:
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.6.0
                   3.0.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Thanks to Sangjin for the contribution and to Allen and Kihwal for additional review!  I committed
this to trunk and 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
>             Fix For: 3.0.0, 2.6.0
>
>         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)

Mime
View raw message