[
https://issues.apache.org/jira/browse/YARN-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838142#comment-16838142
]
Sunil Govindan commented on YARN-9546:
--------------------------------------
Hi [~shuzirra]
As per this patch, you are introducing a new yarn config named
*yarn.service.classpath* and configuring any classpath which are needed for
native service. Since its a new config, its better to a description for this
config like "accepts comma separated values etc" in yarn default xml. and you
can set default value as empty. Initially i thought its a an ENV variable and
hence suggested not to add to yarn-default. However as per current approach, it
makes sense to add to xml.
Other than this, patch looks fine. cc [~billie.rinaldi]
> 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: [email protected]
For additional commands, e-mail: [email protected]
