[ 
https://issues.apache.org/jira/browse/HDFS-13272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16397433#comment-16397433
 ] 

Kihwal Lee commented on HDFS-13272:
-----------------------------------

bq. ... the possibility of this being too few threads ...
The jetty server on datanode is only used for UI and basic servlets. All the 
heavy lifting is now done by the netty-based server.  I think it can even be 
less than 5 for production environments. Rather than making it configurable, it 
might be better to simply reduce it.  This makes sense to branch-3.x.  For 
older branches, there still might be hftp users. Prior to the introduction of 
the netty-based webhdfs server on datanode, the number of jetty threads was 
probably 256.  [~jrottinghuis], do you still use hftp? 

> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to