You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2018/05/10 22:38:00 UTC
[jira] [Commented] (HDFS-13272) DataNodeHttpServer to have
configurable HttpServer2 threads
[ https://issues.apache.org/jira/browse/HDFS-13272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471243#comment-16471243 ]
Chris Douglas commented on HDFS-13272:
--------------------------------------
Thanks [~xkrogen], sorry for the delay.
bq. There were no new failures with the patch applied and it took about the same time to run all of them
{{TestClientProtocolForPipelineRecovery}} also fails on branch-2, the other tests... often pass. This doesn't seem to introduce any regressions.
+1 I committed this
> 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
> Fix For: 2.9.2
>
> Attachments: HDFS-13272-branch-2.000.patch, HDFS-13272-branch-2.001.patch, testout-HDFS-13272.001, testout-branch-2
>
>
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org