-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HBASE-27923 NettyRpcServer may hange if it should skip initial sasl h… #5281
Conversation
🎊 +1 overall
This message was automatically generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice finding!
@@ -125,7 +125,9 @@ protected void initChannel(Channel ch) throws Exception { | |||
initSSL(pipeline, conf.getBoolean(HBASE_SERVER_NETTY_TLS_SUPPORTPLAINTEXT, true)); | |||
} | |||
pipeline.addLast(NettyRpcServerPreambleHandler.DECODER_NAME, preambleDecoder) | |||
.addLast(createNettyRpcServerPreambleHandler()); | |||
.addLast(createNettyRpcServerPreambleHandler()) | |||
.addLast(NettyRpcServerResponseEncoder.HANDLER_NAME, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better add some comments to say that why we need to add encoder here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Apache9 , thanks for review,already added some comments.
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
@@ -31,6 +31,8 @@ | |||
@InterfaceAudience.Private | |||
class NettyRpcServerResponseEncoder extends ChannelOutboundHandlerAdapter { | |||
|
|||
static final String HANDLER_NAME = "NettyRpcServerResponseEncoder"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: rename it as "ENCODER_NAME"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wchevreuil, thanks for review,here I did not name it as "ENCODER_NAME" because it is misleading and is also inconsistent with the naming conventions of other netty handlers, here this name represents NettyRpcServerResponseEncoder
itself,but for other netty handler such as NettyRpcServerPreambleHandle
,NettyRpcServerPreambleHandler.DECODER_NAME
represents decoder handler before it, not represents itself. I have ready renamed it as "NAME" to keep consistent with the naming conventions of other netty handlers. What is your opinion?
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
Thank you @comnetwork, you are planning to merge this to all active branches (till 2.4), correct? |
@virajjasani , I think this problem only exists on 2.6+, because it is introduced by HBASE-27279 and HBASE-27185,which only applied to 2.6+ . However, I would apply the UT to branch-2.4 and branch-2.5 |
#5281) Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Wellington Chevreuil <wchevreuil@apache.rog>
…andshake