[
https://issues.apache.org/jira/browse/HBASE-17908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064273#comment-16064273
]
stack commented on HBASE-17908:
-------------------------------
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.
> Upgrade guava
> -------------
>
> Key: HBASE-17908
> URL: https://issues.apache.org/jira/browse/HBASE-17908
> Project: HBase
> Issue Type: Sub-task
> Components: dependencies
> Reporter: Balazs Meszaros
> Assignee: stack
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-17908.master.001.patch,
> HBASE-17908.master.002.patch, HBASE-17908.master.003.patch,
> HBASE-17908.master.004.patch, HBASE-17908.master.005.patch,
> HBASE-17908.master.006.patch
>
>
> Currently we are using guava 12.0.1, but the latest version is 21.0.
> Upgrading guava is always a hassle because it is not always backward
> compatible with itself.
> Currently I think there are to approaches:
> 1. Upgrade guava to the newest version (21.0) and shade it.
> 2. Upgrade guava to a version which does not break or builds (15.0).
> If we can update it, some dependencies should be removed:
> commons-collections, commons-codec, ...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
