[ 
https://issues.apache.org/jira/browse/HBASE-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245982#comment-16245982
 ] 

Josh Elser commented on HBASE-18943:
------------------------------------

{quote}
It was just a suggestion.
Since stack recently upgraded jetty, HBASE-18224, let's wait for his 
comment/approval.
{quote}

Yeahhh, I think moving back to relying on what Hadoop depends on is a step in 
the wrong direction. Since we know that (presently) Hadoop only uses it for 
HttpServer2 (which we no longer use in HBase), let's control it ourselves. Easy 
steps would be:

* Bundle our own Jetty and use that exclusively (some worries already brought 
up about that)
* Exclude Hadoop's Jetty dependency and just provide our's instead

I don't feel too strongly in either direction.

> 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
>
>         Attachments: 18943.v1.txt
>
>
> 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)

Reply via email to