[
https://issues.apache.org/jira/browse/YARN-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422956#comment-16422956
]
Xuan Gong commented on YARN-1151:
---------------------------------
Thanks for the review. [~rkanter]
bq. for the classpath. If it's a regular jar, there's no reason to extract it.
I agree with this. If we use the FSDownload API call for the
LocalResourceType.ARCHIVE, it will untar it. If we do not want to untar the
jar, we need to support various ResourceTypes. For now and for the simplicity,
let us not handle jar type separately.
bq. We also need a way for these files to be cleaned up if they're not being
used anymore. For instance, if the jar's name is versioned (e.g.
"my-aux-service-1.1.jar"), then every time you update the jar and restart the
NM, it's going to create new local files and never clean up the old ones. We
can probably have it delete anything in the {{nmAuxService}} dir that it's not
loading.
We will delete the old jar files using the deletionService
bq. We need some unit tests.
Added
bq. currently the NM will repeatedly download the tar again and again on every
restart. We should try to figure out a way not to do that.
We will handle it by checking the lastModifiedTime of the remote files.
> Ability to configure auxiliary services from HDFS-based JAR files
> -----------------------------------------------------------------
>
> Key: YARN-1151
> URL: https://issues.apache.org/jira/browse/YARN-1151
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager
> Affects Versions: 2.1.0-beta, 2.9.0
> Reporter: john lilley
> Assignee: Xuan Gong
> Priority: Major
> Labels: auxiliary-service, yarn
> Attachments: YARN-1151.1.patch, YARN-1151.2.patch, YARN-1151.3.patch,
> YARN-1151.4.patch, YARN-1151.branch-2.poc.2.patch,
> YARN-1151.branch-2.poc.3.patch, YARN-1151.branch-2.poc.patch, [YARN-1151]
> [Design] Configure auxiliary services from HDFS-based JAR files.pdf
>
>
> I would like to install an auxiliary service in Hadoop YARN without actually
> installing files/services on every node in the system. Discussions on the
> user@ list indicate that this is not easily done. The reason we want an
> auxiliary service is that our application has some persistent-data components
> that are not appropriate for HDFS. In fact, they are somewhat analogous to
> the mapper output of MapReduce's shuffle, which is what led me to
> auxiliary-services in the first place. It would be much easier if we could
> just place our service's JARs in HDFS.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
