[YARN-7190] Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.0, 3.0.1, 3.0.2, 3.0.3
• Fix Version/s: YARN-5355_branch2, 3.1.0, 2.9.1, 3.0.3
• Component/s: timelineclient, timelinereader, timelineserver
• Target Version/s: 3.1.0
• Hadoop Flags: Incompatible change, Reviewed
• Release Note: Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath.
• Assignee: Varun Saxena
• Reporter: Vrushali C
• Created: 13/Sep/17 16:22
• Updated: 01/Sep/18 22:57
• Resolved: 15/Dec/17 16:58

Description

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

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

Issue Links

• relates to: HBASE-20502 Document HBase incompatible with Yarn 2.9.0 and 3.0.x due to YARN-7190
• relates to: HBASE-21036 Upgrade our hadoop 3 dependency to 3.1.1