[
https://issues.apache.org/jira/browse/YARN-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457065#comment-16457065
]
Billie Rinaldi commented on YARN-7799:
--------------------------------------
Attached patch 2 based on the discussion. In the case when the calling user is
in yarn.admin.acl, we don't need to check whether yarn.service.framework.path
has been preconfigured. If the hdfs admin user has given the yarn user
permission to write to /yarn-services, the file can be uploaded. If not, the
upload will fail. Oh, I just noticed I forgot to check for executable
permission on the parent directories. I'll upload patch 3 for that.
> 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, YARN-7799.2.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]
