hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10893) isolated classloader on the client side
Date Wed, 20 Aug 2014 01:04:31 GMT

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

Sangjin Lee updated HADOOP-10893:
---------------------------------

    Attachment: HADOOP-10893.patch

Updated the patch with the following changes:
- fixed RunJar.useClientClassLoader()
- renamed the test classes
- updated the patch to apply after HADOOP-9902

I'll post a separate patch for branch-2 later.

> 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.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