[
https://issues.apache.org/jira/browse/HBASE-28312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-28312.
-------------------------------
Fix Version/s: 2.6.0
2.4.18
2.5.8
3.0.0-beta-2
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to all active branches.
Thanks [~bbeaudreault] for reviewing!
> 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, 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)
