-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-25586 Fix HBASE-22492 on branch-2 (SASL GapToken) #2961
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
Conversation
ServerCall.java: calling wrapWithSasl() was moved to getResponse(), so the SASL wrapping is delayed until the reply is sent back to the client.
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
Excellent find! Can the reproduction code be used to add a test? |
|
🎊 +1 overall
This message was automatically generated. |
It would be very problematic, because:
|
|
retest |
What about just the code you have used to reproduce this, provided "as-is"? Having been here before, I can understand how tough it is to just get to this problem. |
petersomogyi
left a comment
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.
lgtm
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
ServerCall.java: calling wrapWithSasl() was moved to getResponse(), so the SASL wrapping is delayed until the reply is sent back to the client. Signed-off-by: Peter Somogyi <[email protected]>
ServerCall.java: calling wrapWithSasl() was moved to getResponse(), so the SASL wrapping is delayed until the reply is sent back to the client. Signed-off-by: Peter Somogyi <[email protected]>
ServerCall.java: calling wrapWithSasl() was moved to getResponse(), so the SASL wrapping is delayed until the reply is sent back to the client. Signed-off-by: Peter Somogyi <[email protected]>
ServerCall.java: calling wrapWithSasl() was moved to getResponse(), so the SASL wrapping is delayed until the reply is sent back to the client. Signed-off-by: Peter Somogyi <[email protected]>
Just noticed that the test runner is attached to https://issues.apache.org/jira/browse/HBASE-25586 |
ServerCall.java: calling wrapWithSasl() was moved to getResponse(), so the SASL wrapping is delayed until the reply is sent back to the client. Signed-off-by: Peter Somogyi <[email protected]> (cherry picked from commit ec9995c) Change-Id: Ibcd471082e617a0d2fda7f4dcbf395cd8022189c
ServerCall.java: calling wrapWithSasl() was moved to getResponse(), so
the SASL wrapping is delayed until the reply is sent back to the client.