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

stack commented on HBASE-18271:
-------------------------------

Copied over from the sibling guava shading issue:

bq. The netty failures are interesting. The netty-all jar has a .so in it. 
There is facility in netty to support relocation but you need to rename the .so 
which is kind of messy bundling up the fat jar. I changed hbase-thirdparty to 
do this but you have to tell netty about the relocation on the command-line via 
system property. Gruesome detail added to the hbase-shaded-thirdparty/pom.xml. 
Need to come back to netty when we do its reolcation and ensure that we are 
picking up the native epoll. TODO. Meantime, new hbase-thirdparty with the 
proper relocation seems to fix the failure that was happening on linux (not on 
mac os x). Will put up a new patch in a mo to get a new run.

> Shade netty
> -----------
>
>                 Key: HBASE-18271
>                 URL: https://issues.apache.org/jira/browse/HBASE-18271
>             Project: HBase
>          Issue Type: Sub-task
>          Components: rpc
>    Affects Versions: 2.0.0
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0-beta-1
>
>
> Our new prefatory project, hbase-thirdparty, includes a relocated netty 
> 4.1.12. This issue is about changing references in hbase to make use of this 
> shaded netty. This way we will take ourselves out of the clashing library 
> saga and change netty as we see fit.
> One kink is the inclusion inside the netty-all jar of an .so. We need to make 
> sure it gets loaded and that on linux we are doing native epoll; all should 
> be in place to do this but need to add a system property to bin/hbase for 
> netty to pick up. TODO as part of this issue. See tail of upgrade guava 
> sibling issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to