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

Posted to dev@hbase.apache.org by "Wellington Chevreuil (Jira)" <ji...@apache.org> on 2020/07/20 11:45:00 UTC

[jira] [Resolved] (HBASE-24747) Log an ERROR if HBaseSaslRpcServer initialisation fails with an uncaught exception

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

Wellington Chevreuil resolved HBASE-24747.
------------------------------------------
    Resolution: Fixed

> Log an ERROR if HBaseSaslRpcServer initialisation fails with an uncaught exception
> ----------------------------------------------------------------------------------
>
>                 Key: HBASE-24747
>                 URL: https://issues.apache.org/jira/browse/HBASE-24747
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 3.0.0-alpha-1, 2.3.1, 2.4.0
>            Reporter: Wellington Chevreuil
>            Assignee: Wellington Chevreuil
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.3.1, 2.4.0
>
>
> In ServerRpcConnection.saslReadAndProcess, if an uncaught exception happens while initialising HBaseSaslRpcServer, the same gets swallowed inside netty and never explicitly logged on RegionServer logs. With the introduction of pluggable sasl server providers by HBASE-23347, this situation can become more frequent with the addition of custom providers, if those cause HBaseSaslRpcServer to fail, that should be logged in ServerRpcConnection.saslReadAndProces.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)