hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-18271) Shade netty
Date Sun, 13 Aug 2017 19:53:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-18271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-18271:
--------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Pushed to branch-2 and master.

Will keep an eye out for case where we are NOT using the .so by default. Filed a task to check
on it as blocker against 2.0

> 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: Blocker
>             Fix For: 2.0.0
>
>         Attachments: HBASE-18271.master.001.patch, HBASE-18271.master.002.patch, HBASE-18271.master.003.patch,
HBASE-18271.master.004.patch, HBASE-18271.master.005.patch, HBASE-18271-Shade-netty-Purge-mention-of-netty-all.003.patch
>
>
> 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)

Mime
View raw message