[
https://issues.apache.org/jira/browse/HBASE-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839867#comment-16839867
]
Sean Mackrory commented on HBASE-22393:
---------------------------------------
The javax stuff turned out to be from jsr305 not being excluded everywhere -
it's actually a banned dependency in HBase proper.
I've removed the slf4j-log4j and log4j JARs from any involvement in the shading
after discussing the specifics with [~busbey]. slf4j-api is still included.
Looks good to me, but I can't conveniently deploy this onto a real cluster,
right now. I trust [~wchevreuil] can kindly give this a good test much quicker
than I can :)
> 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
> Components: Filesystem Integration
> Affects Versions: hbase-filesystem-1.0.0-alpha1
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Critical
> Fix For: hbase-filesystem-1.0.0-alpha1
>
> Attachments:
> 0001-HBASE-22393-HBOSS-Shade-dependencies-to-prevent-conf.patch,
> HBASE-22393.001.patch, HBASE-22393.002.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)
