hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhangduo (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5270) Use thread pools in the datenode daemons
Date Sun, 10 May 2015 12:10:00 GMT

     [ https://issues.apache.org/jira/browse/HDFS-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

zhangduo updated HDFS-5270:
    Status: Patch Available  (was: Reopened)

Use thread pool in DataXceiverServer.
Introduce a XceiverStopper to stop a DataXceiver instead of killing thread directly.

And there is a hole that PacketResponder still uses Daemon. But I think the patch is big enough
for reviewing now so put it here first. I will do it in the next patch.


> 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: zhangduo
>              Labels: BB2015-05-TBR
>         Attachments: HDFS-5270.000.patch, HDFS-5270.2.patch, HDFS-5270.3.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

View raw message