[
https://issues.apache.org/jira/browse/YARN-6771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092568#comment-16092568
]
Jongyoul Lee commented on YARN-6771:
------------------------------------
Thanks for the reply. I'm developing cluster manager feature in Apache
Zeppelin. I've tried to use Yarn Client to communicate with Yarn cluster.
Avoiding conflicts of dependencies, I wanted to use custom classloader for
initializing yarn client in the Zeppelin's server process, but it failed
because this implementation uses system classloader even I set the custom
classloader in the Configuration. I changed my implementation to include hadoop
libs into process directly but I think we need to change it to work correctly.
> Use classloader inside configuration class to make new classes
> ---------------------------------------------------------------
>
> Key: YARN-6771
> URL: https://issues.apache.org/jira/browse/YARN-6771
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.8.1, 3.0.0-alpha4
> Reporter: Jongyoul Lee
> Fix For: 2.8.2
>
> Attachments: YARN-6771-1.patch, YARN-6771-2.patch, YARN-6771.patch
>
>
> While running {{RpcClientFactoryPBImpl.getClient}},
> {{RpcClientFactoryPBImpl}} uses {{localConf.getClassByName}}. But in case of
> using custom classloader, we have to use {{conf.getClassByName}} because
> custom classloader is already stored in {{Configuration}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
