[
https://issues.apache.org/jira/browse/HDDS-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852964#comment-16852964
]
Elek, Marton commented on HDDS-1525:
------------------------------------
bq. Remove the libs\ prefix for ozone classes in legacy jar POM
The libs folder guarantee the separation between the two classloader. Without
the libs folder all the classes can be loaded by any classloader. Classes from
the lib/ location can't be located by the default class loader just the
filtered classloader.
Other parts of the patch looks good to me, thanks to fix. [~xyao]. Do we need
to commit it to the trunk?
Note: I am not very happy with the current (=current on the trunk) solution.
Originally we choose the custom classloader approach to keep the project
structure simple. But this is just more and more complex. I am wondering how is
it possible to achieve similar results with multiple shaded projects.
> Mapreduce failure when using Hadoop 2.7.5
> -----------------------------------------
>
> Key: HDDS-1525
> URL: https://issues.apache.org/jira/browse/HDDS-1525
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Filesystem
> Affects Versions: 0.4.0
> Reporter: Sammi Chen
> Priority: Major
> Attachments: HDDS-1525.poc.patch, teragen.log
>
>
> Integrate Ozone(0.4 branch) with Hadoop 2.7.5, "hdfs dfs -ls /" can pass,
> while teragen failed.
> When add -verbose:class to java options, it shows that class KeyProvider is
> loaded twice by different classloader while it is only loaded once when
> execute "hdfs dfs -ls /"
> All jars under share/ozone/lib are added into hadoop classpath except ozone
> file system current lib jar.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
