You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Varun Saxena (JIRA)" <ji...@apache.org> on 2017/10/03 09:17:00 UTC
[jira] [Comment Edited] (YARN-7190) Ensure only NM classpath in 2.x
gets TSv2 related hbase jars, not the user classpath
[ https://issues.apache.org/jira/browse/YARN-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189433#comment-16189433 ]
Varun Saxena edited comment on YARN-7190 at 10/3/17 9:16 AM:
-------------------------------------------------------------
bq. hadoop-yarn-server-timelineservice-hbase-tests-3.1.0-SNAPSHOT.jar is appearing directly under yarn folder
I had thought of moving it to test folder but as hadoop-yarn-server-tests, which is a test project too, was also directly under yarn folder as well, so left it as it is.
As we are going to place our jars in a separate folder "timelineservice" now, I was also thinking to move it to a separate test folder.
bq. Are you going to place Ats1/1.5 server jars as well in this folder?
No. That would be an incompatible change for stable feature even though nobody ideally should be using the server side jars. We should to be honest separate out client and server jars but that would have to be discussed and handled as part of another JIRA. As part of this JIRA, we will take care only of newly added jars by us.
was (Author: varun_saxena):
bq. hadoop-yarn-server-timelineservice-hbase-tests-3.1.0-SNAPSHOT.jar is appearing directly under yarn folder
I had thought of moving it to test folder but as hadoop-yarn-server-tests, which is a test project too, was also directly under yarn folder as well, so left it as it is.
As we are going to place our jars in a separate folder, I was also thinking to move it to a separate test folder.
bq. Are you going to place Ats1/1.5 server jars as well in this folder?
No. That would be an incompatible change for stable feature even though nobody ideally should be using the server side jars. We should to be honest separate out client and server jars but that would have to be discussed and handled as part of another JIRA. As part of this JIRA, we will take care only of newly added jars by us.
> Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath
> ------------------------------------------------------------------------------------
>
> Key: YARN-7190
> URL: https://issues.apache.org/jira/browse/YARN-7190
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineclient, timelinereader, timelineserver
> Reporter: Vrushali C
> Assignee: Varun Saxena
>
> [~jlowe] had a good observation about the user classpath getting extra jars in hadoop 2.x brought in with TSv2. If users start picking up Hadoop 2,x's version of HBase jars instead of the ones they shipped with their job, it could be a problem.
> So when TSv2 is to be used in 2,x, the hbase related jars should come into only the NM classpath not the user classpath.
> Here is a list of some jars
> {code}
> commons-csv-1.0.jar
> commons-el-1.0.jar
> commons-httpclient-3.1.jar
> disruptor-3.3.0.jar
> findbugs-annotations-1.3.9-1.jar
> hbase-annotations-1.2.6.jar
> hbase-client-1.2.6.jar
> hbase-common-1.2.6.jar
> hbase-hadoop2-compat-1.2.6.jar
> hbase-hadoop-compat-1.2.6.jar
> hbase-prefix-tree-1.2.6.jar
> hbase-procedure-1.2.6.jar
> hbase-protocol-1.2.6.jar
> hbase-server-1.2.6.jar
> htrace-core-3.1.0-incubating.jar
> jamon-runtime-2.4.1.jar
> jasper-compiler-5.5.23.jar
> jasper-runtime-5.5.23.jar
> jcodings-1.0.8.jar
> joni-2.1.2.jar
> jsp-2.1-6.1.14.jar
> jsp-api-2.1-6.1.14.jar
> jsr311-api-1.1.1.jar
> metrics-core-2.2.0.jar
> servlet-api-2.5-6.1.14.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org