[
https://issues.apache.org/jira/browse/HBASE-28312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807994#comment-17807994
]
Hudson commented on HBASE-28312:
--------------------------------
Results for branch branch-2.6
[build #34 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/34/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/34/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/34/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/34/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/34/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> The bad auth exception can not be passed to client rpc calls properly
> ---------------------------------------------------------------------
>
> Key: HBASE-28312
> URL: https://issues.apache.org/jira/browse/HBASE-28312
> Project: HBase
> Issue Type: Bug
> Components: Client, IPC/RPC
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.6.0, 2.4.18, 2.5.8, 3.0.0-beta-2
>
>
> Found this when implementing HBASE-25051.
> Basically there are 2 problems:
> # IPCUtil.isFatalConnectionException only checks whether class name matches,
> so if we use a sub class for FatalConnectionException, it will return false
> which makes the logic incorrect.
> # In BlockingRpcConnection, we will first check whether there is a call with
> the id but since we will pass -1 as call id for bad preamble header, we will
> return earlier without actually checking the error response.
> This will not introduce big trouble in production as the call will still fail
> with connection closed exception, but still worth to fix, anyway.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
