[ https://issues.apache.org/jira/browse/HBASE-28384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821524#comment-17821524 ]
Hudson commented on HBASE-28384: -------------------------------- Results for branch HBASE-28384-branch-2 [build #8 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/HBASE-28384-branch-2/8/]: (/) *{color:green}+1 overall{color}* ---- details (if available): (/) {color:green}+1 source release artifact{color} -- See build output for details. (/) {color:green}+1 client integration test{color} > Client ingegration tests fails for branch-2/branch-2.6 > ------------------------------------------------------ > > Key: HBASE-28384 > URL: https://issues.apache.org/jira/browse/HBASE-28384 > Project: HBase > Issue Type: Bug > Components: hadoop3, jenkins > Reporter: Duo Zhang > Assignee: Duo Zhang > Priority: Major > > In HBASE-28331, we fixed the problem that we should use the latest hadoop3 > tarballs, for generating hdfs-site.xml. > But for branch-2.x, we still use hadoop2 when compiling hbase by default, so > there is no org.apache.hadoop.ipc.ProtobufRpcEngine2 class. But the hadoop > 3.3.x will generate hdfs-site.xml with this config, then leads to the failure > of hbase start up. > Should we change to build with hadoop3 while running on top of hadoop3? Since > for branch-2.x, we will publish artifacts for hadoop3. -- This message was sent by Atlassian Jira (v8.20.10#820010)