hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gour Saha (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-7799) YARN Service dependency follow up work
Date Tue, 23 Jan 2018 23:43:00 GMT
Gour Saha created YARN-7799:
-------------------------------

             Summary: 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


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: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org


Mime
View raw message