[
https://issues.apache.org/jira/browse/HDFS-10423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320768#comment-15320768
]
Nicolae Popa commented on HDFS-10423:
-------------------------------------
Patch was manually tested locally and passed. See the attached notes.
I generated http requests of various sizes (1024 2048 4096 8192 8193 16384
32768 44443 44444 44445 65536 65537) in bytes and observed the results in the
following scenarios:
1) before the patch
2) after the patch
3) with the export HTTPFS_MAX_HTTP_HEADER_SIZE=44444 in etc/hadoop/httpfs-env.sh
In testing-before-HTTP-10423.txt we can see it starts failing after a HTTP 8192
request
In testing-after-HTTP-10423.txt we can see it starts failing after a HTTP
65536 request since this is the new default (as expected)
I also run a test setting export HTTPFS_MAX_HTTP_HEADER_SIZE=44444 in
etc/hadoop/httpfs-env.sh and the behavior was as expected. It worked with an
HTTP requests up to 44444 bytes and failed with a request of 44445 bytes (as
expected). (see testing-after-HDFS-10423_withCustomHeader44444.txt)
> Increase default value of httpfs maxHttpHeaderSize
> --------------------------------------------------
>
> Key: HDFS-10423
> URL: https://issues.apache.org/jira/browse/HDFS-10423
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 2.6.4, 3.0.0-alpha1
> Reporter: Nicolae Popa
> Priority: Minor
> Attachments: HDFS-10423.01.patch, HDFS-10423.02.patch,
> testing-after-HDFS-10423.txt,
> testing-after-HDFS-10423_withCustomHeader44444.txt,
> testing-before-HDFS-10423.txt
>
>
> The Tomcat default value of maxHttpHeaderSize is 8k, which is too low for
> certain Hadoop workloads in kerberos enabled environments. This JIRA will to
> change it to 65536 in server.xml
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
