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

Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2024/02/26 13:10:00 UTC

[jira] [Assigned] (HBASE-28384) Client ingegration tests fails for branch-2/branch-2.6

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

Duo Zhang reassigned HBASE-28384:
---------------------------------

    Assignee: Duo Zhang

> 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)