-
Notifications
You must be signed in to change notification settings - Fork 29k
[MINOR] Add requestHeaderSize debug log #25045
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
|
cc @attilapiros |
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.
Please update the PR description. The following description is improper because this is not tested by the existing UT. In this case, you had better describe how to see the debug log you added. It's for the reviewers and the other community members.
How was this patch tested?
Existing unit tests.
|
@dongjoon-hyun Thanks for investing your time, I've updated. |
|
Test build #107186 has finished for PR 25045 at commit
|
dongjoon-hyun
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.
+1, LGTM. I also checked the debug message manually.
19/07/03 09:32:53 DEBUG JettyUtils: Using requestHeaderSize: 8192
Merged to master/2.4/2.3.
## What changes were proposed in this pull request? `requestHeaderSize` is added in #23090 and applies to Spark + History server UI as well. Without debug log it's hard to find out on which side what configuration is used. In this PR I've added a log message which prints out the value. ## How was this patch tested? Manually checked log files. Closes #25045 from gaborgsomogyi/SPARK-26118. Authored-by: Gabor Somogyi <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit 0b6c2c2) Signed-off-by: Dongjoon Hyun <[email protected]>
## What changes were proposed in this pull request? `requestHeaderSize` is added in #23090 and applies to Spark + History server UI as well. Without debug log it's hard to find out on which side what configuration is used. In this PR I've added a log message which prints out the value. ## How was this patch tested? Manually checked log files. Closes #25045 from gaborgsomogyi/SPARK-26118. Authored-by: Gabor Somogyi <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit 0b6c2c2) Signed-off-by: Dongjoon Hyun <[email protected]>
attilapiros
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
## What changes were proposed in this pull request? `requestHeaderSize` is added in apache#23090 and applies to Spark + History server UI as well. Without debug log it's hard to find out on which side what configuration is used. In this PR I've added a log message which prints out the value. ## How was this patch tested? Manually checked log files. Closes apache#25045 from gaborgsomogyi/SPARK-26118. Authored-by: Gabor Somogyi <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit 0b6c2c2) Signed-off-by: Dongjoon Hyun <[email protected]>
## What changes were proposed in this pull request? `requestHeaderSize` is added in apache#23090 and applies to Spark + History server UI as well. Without debug log it's hard to find out on which side what configuration is used. In this PR I've added a log message which prints out the value. ## How was this patch tested? Manually checked log files. Closes apache#25045 from gaborgsomogyi/SPARK-26118. Authored-by: Gabor Somogyi <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit 0b6c2c2) Signed-off-by: Dongjoon Hyun <[email protected]>
What changes were proposed in this pull request?
requestHeaderSizeis added in #23090 and applies to Spark + History server UI as well. Without debug log it's hard to find out on which side what configuration is used.In this PR I've added a log message which prints out the value.
How was this patch tested?
Manually checked log files.