[jira] [Comment Edited] (HBASE-27185) Rewrite NettyRpcServer to decode rpc request with netty handler

["Andrew Kyle Purtell (Jira)" <ji...@apache.org>]

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

Andrew Kyle Purtell edited comment on HBASE-27185 at 7/17/22 3:08 AM:
----------------------------------------------------------------------

bq. Shall we keep the backports upto branch-2 (2.6.0) only?

+1 to this. Refactors deserve some bake time.

Combined with the TLS RPC, such improvements would make 2.6.0 compelling, and we can get started on 2.6.0 as soon as the 2.5.x code line is up and running. 


was (Author: apurtell):
bq. Shall we keep the backports upto branch-2 (2.6.0) only?

+1 to this. 

Combined with the TLS RPC, such improvements would make 2.6.0 compelling, and we can get started on it as soon as the 2.5.x code line is up and running. 

> 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
>            Priority: Major
>
> 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)