[
https://issues.apache.org/jira/browse/HBASE-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244477#comment-16244477
]
Josh Elser commented on HBASE-18943:
------------------------------------
bq. Since we don't use mortbay, and don't exclude it either, hadoop sneaks
it's own jetty in.
Do we know why hadoop-common is polluting our classpath with their version of
Jetty anyways? It seems like bad dependency management on their part to let
this filter down into us (e.g. why would downstream need an HTTP server library
to act as a Hadoop client?)
A quick glance shows that HttpServer2 is contained in hadoop-common which is
the reason this dependency exists. Not sure if we can impose on Hadoop to
introduce a module that their components that depend on to avoid getting pulled
in by hdfs-client/hadoop-common.
> Cannot start mini dfs cluster using hadoop-3 in test due to NoSuchMethodError
> in jetty
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-18943
> URL: https://issues.apache.org/jira/browse/HBASE-18943
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Priority: Blocker
> Fix For: 2.0.0-beta-1
>
>
> When starting mini dfs cluster against hadoop-3:
> {code}
> dfsCluster = startMiniDFSCluster(numDataNodes, dataNodeHosts);
> {code}
> The above call would end up with:
> {code}
> java.lang.NoSuchMethodError:
> org.eclipse.jetty.server.session.SessionHandler.getSessionManager()Lorg/eclipse/jetty/server/SessionManager;
> at org.apache.hadoop.hbase.client.TestHCM.setUpBeforeClass(TestHCM.java:251)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
