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

Hudson commented on HBASE-27185:
--------------------------------

Results for branch master
        [build #645 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/645/]: 
(/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/645/General_20Nightly_20Build_20Report/]






(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/645/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/645/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}


> Rewrite NettyRpcServer to decode rpc request with netty handler
> ---------------------------------------------------------------
>
>                 Key: HBASE-27185
>                 URL: https://issues.apache.org/jira/browse/HBASE-27185
>             Project: HBase
>          Issue Type: Improvement
>          Components: netty, rpc
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 2.6.0, 3.0.0-alpha-4
>
>
> This is a follow on issue of HBASE-26708.
> The memory leaks happens in the saslReadAndProcess method. It does not follow 
> a typical netty style so it is more likely to introduce bugs.
> Since we agree that NettyRpcServer is the future and SimpleRpcServer should 
> be deprecated and finally removed, let's first implement dedicated rpc 
> request decoder for netty.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to