[ 
https://issues.apache.org/jira/browse/HBASE-27065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552162#comment-17552162
 ] 

Duo Zhang commented on HBASE-27065:
-----------------------------------

All MR UTs are broken after the changes here...

{noformat}
java.lang.NoClassDefFoundError: 
org/fusesource/leveldbjni/internal/NativeDB$DBException
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:348)
        at 
org.apache.hadoop.conf.Configuration.getClassByNameOrNull(Configuration.java:2532)
        at 
org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2497)
        at 
org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2593)
        at 
org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2619)
        at 
org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices.serviceInit(AuxServices.java:270)
        at 
org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
        at 
org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:108)
        at 
org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.serviceInit(ContainerManagerImpl.java:318)
{noformat}

https://ci-hbase.apache.org/job/HBase-Flaky-Tests/job/master/3650/testReport/junit/org.apache.hadoop.hbase.mapreduce/TestHBaseMRTestingUtility/testMRYarnConfigsPopulation/

Seems we need the leveldbjni-all dependency?

> Build against Hadoop 3.3.3
> --------------------------
>
>                 Key: HBASE-27065
>                 URL: https://issues.apache.org/jira/browse/HBASE-27065
>             Project: HBase
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 2.5.0
>            Reporter: Andrew Kyle Purtell
>            Assignee: Andrew Kyle Purtell
>            Priority: Major
>             Fix For: 2.5.0, 3.0.0-alpha-3
>
>
> When building against Hadoop 3.3.3 and any future version of Hadoop 
> incorporating reload4j, the new Enforcer rule we have active in branch-2.5 
> and up to exclude other logging frameworks besides log4j2 will trigger. We 
> need to add exclusions to prevent that from happening so the build will 
> succeed.
> Tested with {{mvn clean install assembly:single -DskipTests 
> -Dhadoop-three.version=3.3.3}} on master branch and with {{mvn clean install 
> assembly:single -DskipTests -Dhadoop.profile=3.0 
> -Dhadoop-three.version=3.3.3}} on branch-2.5. 
> I also needed to exclude leveldbjni-all via hadoop-hdfs to avoid a LICENSE 
> file generation error. hadoop-hdfs is messy and exports this among findbugs 
> and other clutter. Anyway, better to exclude something we do not require than 
> add an unnecessary supplemental model. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to