[ https://issues.apache.org/jira/browse/HBASE-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839527#comment-16839527 ]
Sean Busbey commented on HBASE-22393: ------------------------------------- yep, no shading logging libraries or things that don't play well with shading. here's the set we use in the main project: https://github.com/apache/hbase/blob/68f14c19ff79e36b17e99c7e848c19ce5e0164d5/hbase-shaded/pom.xml#L134 > 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: 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)