You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/09/16 07:46:20 UTC

[jira] [Commented] (IGNITE-3909) Hadoop: invalid classloader definition delegation logic.

    [ https://issues.apache.org/jira/browse/IGNITE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15495667#comment-15495667 ] 

Vladimir Ozerov commented on IGNITE-3909:
-----------------------------------------

Looks like this is now what we really need. Instead, we should fully isolate Hadoop module along with all it's dependencies. To achieve this we should modify our source code and scripts so that JVM process receive classpath without Hadoop module and Hadoop dependencies, and only {{HadoopClassLoader}} has access to them.

> Hadoop: invalid classloader definition delegation logic.
> --------------------------------------------------------
>
>                 Key: IGNITE-3909
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3909
>             Project: Ignite
>          Issue Type: Bug
>          Components: hadoop
>    Affects Versions: 1.7
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>            Priority: Critical
>             Fix For: 1.8
>
>
> Currently we load explicitly only some {{org.apache.ignite}} and {{org.apache.hadoop}} classes.
> For this reason 3rd-party classes are always loaded by parent classloader, what leads to various weird exception.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)