[
https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264399#comment-15264399
]
Sangjin Lee commented on YARN-4577:
-----------------------------------
If you push more into {{AuxiliaryServiceWithCustomClassLoader}} from
{{AuxServices}}, it may give you more opportunities to do targeted unit tests.
Just FYI, in case of {{TestRunJar}}, I created a few test classes
({{ClassLoaderCheckMain}}, etc.), created a jar on the fly
({{makeClassLoaderTestJar()}}), changed the system classes to include/exclude
some of these test classes using the override, and test scenarios. Your mileage
may vary.
> Enable aux services to have their own custom classpath/jar file
> ---------------------------------------------------------------
>
> Key: YARN-4577
> URL: https://issues.apache.org/jira/browse/YARN-4577
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.8.0
> Reporter: Xuan Gong
> Assignee: Xuan Gong
> Attachments: YARN-4577.1.patch, YARN-4577.2.patch,
> YARN-4577.20160119.1.patch, YARN-4577.20160204.patch,
> YARN-4577.20160428.patch, YARN-4577.3.patch, YARN-4577.3.rebase.patch,
> YARN-4577.4.patch, YARN-4577.5.patch, YARN-4577.poc.patch
>
>
> Right now, users have to add their jars to the NM classpath directly, thus
> put them on the system classloader. But if multiple versions of the plugin
> are present on the classpath, there is no control over which version actually
> gets loaded. Or if there are any conflicts between the dependencies
> introduced by the auxiliary service and the NM itself, they can break the NM,
> the auxiliary service, or both.
> The solution could be: to instantiate aux services using a classloader that
> is different from the system classloader.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
