[
https://issues.apache.org/jira/browse/HBASE-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244649#comment-16244649
]
Appy commented on HBASE-18943:
------------------------------
{quote}
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
{quote}
'sneak' was probably wrong choice of word on my part. Should have said 'since
we don't have org.mortbay.jetty, hadoop bring it on its own'. Difference being,
mortbay.jetty is needed by hadoop, since we don't provide it, hadoop bring it
in transitively.
If we don't have the bandwidth to shade it in third-party right now (like stack
said, can get messy), a quick solution would be to downgrade our own jetty
version from 9.4.6 to 9.3.11. We can do the shading in 2.1 release.
> 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)
