You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Gergely Pollak (JIRA)" <ji...@apache.org> on 2019/05/10 14:57:00 UTC
[jira] [Assigned] (YARN-9546) Add configuration option for yarn
services AM classpath
[ https://issues.apache.org/jira/browse/YARN-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gergely Pollak reassigned YARN-9546:
------------------------------------
Assignee: Gergely Pollak
Attachment: YARN-9546.001.patch
> Add configuration option for yarn services AM classpath
> -------------------------------------------------------
>
> Key: YARN-9546
> URL: https://issues.apache.org/jira/browse/YARN-9546
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Gergely Pollak
> Assignee: Gergely Pollak
> Priority: Major
> Attachments: YARN-9546.001.patch
>
>
> For regular containers we have the yarn.application.classpath property, which allows users to add extra elements to the container's classpath.
> However yarn services deliberately ignores this property to avoid incompatible class collision. However on systems where the configuration files for containers are located other than the path stored in $HADOOP_CONF_DIR, there is no way to modify the classpath to include other directories with the actual configuration.
> Suggestion let's create a new property which allows us to add extra elements to the classpath generated for YARN service AM containers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org