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

2020-07-21 Thread Hudson (Jira) 


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

Hudson commented on HBASE-24747:


Results for branch branch-2.3
[build #188 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/188/]: 
(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/branch-2.3/188/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/branch-2.3/188/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/188/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/branch-2.3/188/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
>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)

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

2020-07-20 Thread Hudson (Jira) 


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

Hudson commented on HBASE-24747:


Results for branch branch-2
[build #2752 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2752/]: 
(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/branch-2/2752/General_20Nightly_20Build_20Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2752/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2752/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/branch-2/2752/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
>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)

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

2020-07-18 Thread Hudson (Jira) 


[ 
https://issues.apache.org/jira/browse/HBASE-24747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)