[
https://issues.apache.org/jira/browse/YARN-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456647#comment-16456647
]
Billie Rinaldi commented on YARN-7799:
--------------------------------------
{quote}Can this new feature create a problem with prefix directory file
permission that prevent other people from accessing the dependency jar file?
{quote}
This is a good point. Typically the hdfs user would upload the dependency
tarball with the enableFastLaunch command and other users would only be allowed
to read the file. If we make the change to allow the RM to automatically upload
the file, at a minimum we'd be changing how the directory permissions would
need to be set up, since the yarn user would need to be given permission to
write the file. I was reluctant to make the auto upload change anyway, so I am
thinking about removing this change from the patch and only fixing the default
behavior of enableFastLaunch. (Removing auto upload would only be a one line
change in the patch, and it would also address Gour's suggestions.) What do you
think, [~gsaha] [~eyang]?
> YARN Service dependency follow up work
> --------------------------------------
>
> Key: YARN-7799
> URL: https://issues.apache.org/jira/browse/YARN-7799
> Project: Hadoop YARN
> Issue Type: Bug
> Components: client, resourcemanager
> Reporter: Gour Saha
> Assignee: Billie Rinaldi
> Priority: Critical
> Attachments: YARN-7799.1.patch
>
>
> As per [~jianhe] these are some followup items that make sense to do after
> YARN-7766. Quoting Jian's comment below -
> Currently, if user doesn't supply location when run yarn app
> -enableFastLaunch, the jars will be put under this location
> {code}
> hdfs:///yarn-services/<versionId>/service-dep.tar.gz
> {code}
> Since API server is embedded in RM, should RM look for this location too if
> "yarn.service.framework.path" is not specified ?
> And if "yarn.service.framework.path" is not specified and still the file
> doesn't exist at above default location, I think RM can try to upload the
> jars to above default location instead, currently RM is uploading the jars to
> the location defined by below code. This folder is per app and also
> inconsistent with CLI location.
> {code}
> protected Path addJarResource(String serviceName,
> Map<String, LocalResource> localResources)
> throws IOException, SliderException {
> Path libPath = fs.buildClusterDirPath(serviceName);
> {code}
> By doing this, the next time a submission request comes, RM doesn't need to
> upload the jars again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
