[
https://issues.apache.org/jira/browse/HADOOP-14347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Zhuge updated HADOOP-14347:
--------------------------------
Attachment: HADOOP-14347.002.patch
Patch 002
* HttpServer2 reads a new property {{hadoop.http.accept.queue.size}} and sets
the connection backlog. The property default is 128 which is the current
hard-coded value.
* Add {{hadoop.http.accept.queue.size}} with default 128 to core-default.xml
* Refactor core-default.xml, kms-default.xml, and httpfs-default.xml
** Create a section {{HTTP properties}} in core-default.xml, add related
{{hadoop.http.*}} properties there. The default values match those in
HttpServer2.
** kms-default.xml only maintains KMS overrides, e.g., max thread is 1000,
accept queue size is 500, matching the Tomcat values in branch-2.
** httpfs-default.xml only maintain HttpFS overrides, e.g., max threads is 150,
matching the Tomcat value in branch-2.
> Make KMS and HttpFS Jetty connection backlog configurable
> ---------------------------------------------------------
>
> Key: HADOOP-14347
> URL: https://issues.apache.org/jira/browse/HADOOP-14347
> Project: Hadoop Common
> Issue Type: Improvement
> Components: kms
> Affects Versions: 3.0.0-alpha2
> Reporter: John Zhuge
> Assignee: John Zhuge
> Attachments: HADOOP-14347.001.patch, HADOOP-14347.002.patch
>
>
> HADOOP-14003 enabled the customization of Tomcat attribute {{protocol}},
> {{acceptCount}}, and {{acceptorThreadCount}} for KMS in branch-2. See
> https://tomcat.apache.org/tomcat-6.0-doc/config/http.html.
> KMS switched from Tomcat to Jetty in trunk. Only {{acceptCount}} has a
> counterpart in Jetty, {{acceptQueueSize}}. See
> http://www.eclipse.org/jetty/documentation/9.3.x/configuring-connectors.html.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
