[
https://issues.apache.org/jira/browse/HDFS-13272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16397454#comment-16397454
]
Erik Krogen commented on HDFS-13272:
------------------------------------
This is mostly motivated by the desire to reduce the thread consumption of a
MiniDFSCluster, so configurability is nice, but reducing it to 5 would only 2
more than the minimum so probably acceptable. However, that has the annoyance
that the max must be {{>= 1 + acceptorCount + selectorCount}}, and by default
{{acceptorCount = numCores/8}} and {{selectorCount = numCores/2}}, so with a
default of 5 we would need to modify the acceptor/selector values as well on
higher core machines - those defaults are both capped at 4 (see HADOOP-15311
for the calculations) which is why 10 as a default is safe.
> DataNodeHttpServer to have configurable HttpServer2 threads
> -----------------------------------------------------------
>
> Key: HDFS-13272
> URL: https://issues.apache.org/jira/browse/HDFS-13272
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Reporter: Erik Krogen
> Assignee: Erik Krogen
> Priority: Major
>
> In HDFS-7279, the Jetty server on the DataNode was hard-coded to use 10
> threads. In addition to the possibility of this being too few threads, it is
> much higher than necessary in resource constrained environments such as
> MiniDFSCluster. To avoid compatibility issues, rather than using
> {{HttpServer2#HTTP_MAX_THREADS}} directly, we can introduce a new
> configuration for the DataNode's thread pool size.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
