[
https://issues.apache.org/jira/browse/HDFS-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535860#comment-14535860
]
Haohui Mai commented on HDFS-5270:
----------------------------------
The failures are expected. In the write path the DN kills threads during
recovery, which violates the assumption of making a thread pool. The unit tests
are pointing to the exact issue.
In summary I no longer believe that this is a promising direction due to the
inherent complexity and concerns on backward compatibility. It might make more
sense to invest in HDFS-7966 in the longer term.
> Use thread pools in the datenode daemons
> ----------------------------------------
>
> Key: HDFS-5270
> URL: https://issues.apache.org/jira/browse/HDFS-5270
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Labels: BB2015-05-TBR
> Attachments: HDFS-5270.000.patch, HDFS-5270.2.patch,
> TestConcurrentAccess.java
>
>
> The current implementation of the datanode creates a thread when a new
> request comes in. This incurs high overheads for the creation / destruction
> of threads, making the datanode unstable under high concurrent loads.
> This JIRA proposes to use a thread pool to reduce the overheads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
