You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2023/09/13 20:14:00 UTC
[jira] [Updated] (HBASE-28050) RSProcedureDispatcher to fail-fast for krb auth failures
[ https://issues.apache.org/jira/browse/HBASE-28050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viraj Jasani updated HBASE-28050:
---------------------------------
Summary: RSProcedureDispatcher to fail-fast for krb auth failures (was: RSProcedureDispatcher to fail-fast for krb auth issues)
> RSProcedureDispatcher to fail-fast for krb auth failures
> --------------------------------------------------------
>
> Key: HBASE-28050
> URL: https://issues.apache.org/jira/browse/HBASE-28050
> Project: HBase
> Issue Type: Sub-task
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
>
> As discussed on the parent Jira, let's mark the remote procedures fail when we encounter SaslException (GSS initiate failed) as this belongs to the category of known IOException where we are certain that the request has not yet reached to the target regionserver yet.
> This should help release dispatcher threads for other ExecuteProceduresRemoteCall executions.
>
> Example log:
> {code:java}
> 2023-08-25 02:21:02,821 WARN [ispatcher-pool-40777] procedure.RSProcedureDispatcher - request to rs1,61020,1692930044498 failed due to java.io.IOException: Call to address=rs1:61020 failed on local exception: java.io.IOException: org.apache.hbase.thirdparty.io.netty.handler.codec.DecoderException: org.apache.hadoop.ipc.RemoteException(javax.security.sasl.SaslException): GSS initiate failed, try=0, retrying... {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)