You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/07/18 15:58:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17160455#comment-17160455 ]
Hudson commented on HBASE-24747:
--------------------------------
Results for branch master
[build #1788 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1788/]: (x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/master/1788/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1698/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1788/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 report|https://builds.apache.org/job/HBase%20Nightly/job/master/1788/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}
> 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
> Reporter: Wellington Chevreuil
> Assignee: Wellington Chevreuil
> Priority: Major
>
> 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)