You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Sean Mackrory (JIRA)" <ji...@apache.org> on 2019/05/10 16:33:00 UTC

[jira] [Updated] (HBASE-22393) HBOSS: Shade curator to prevent conflict with Hadoop

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

Sean Mackrory updated HBASE-22393:
----------------------------------
    Attachment: HBASE-22393.001.patch

> HBOSS: Shade curator to prevent conflict with Hadoop
> ----------------------------------------------------
>
>                 Key: HBASE-22393
>                 URL: https://issues.apache.org/jira/browse/HBASE-22393
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>            Priority: Major
>         Attachments: HBASE-22393.001.patch
>
>
> Hadoop uses a very old version of Curator, and if it ever ends up in the classpath with HBOSS you can get this:
> {code}Exception in thread "main" java.lang.IllegalAccessError: tried to access method org.apache.curator.framework.recipes.locks.InterProcessMutex.isOwnedByCurrentThread()Z from class org.apache.hadoop.hbase.oss.sync.ZKTreeLockManager{code}
> I think the simplest solution is to just shade Curator.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)