[
https://issues.apache.org/jira/browse/HDFS-11742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993862#comment-15993862
]
Tsz Wo Nicholas Sze commented on HDFS-11742:
--------------------------------------------
Hi Kihwal Lee, let's have a more detailed discussion before reverting HDFS-8818.
HDFS-8818 (a thread pool per datanode pair) is indeed an improvement for the
previous design (a global thread pool) since it limits the number of threads
assigned to a particular datanode pair. Previously, if the first datanode pair
has a lot of pending moves, all the threads will be used to execute the moves
for that pair so that it will be very slow since it cannot utilize the entire
network.
We also has tested the new code a lot and see significant performance
improvement.
Have you tested it with HDFS-11377?
> Revert the core changes from HDFS-8818
> --------------------------------------
>
> Key: HDFS-11742
> URL: https://issues.apache.org/jira/browse/HDFS-11742
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Priority: Blocker
> Attachments: HDFS-11742.branch-2.8.patch, HDFS-11742.branch-2.patch,
> HDFS-11742.trunk.patch
>
>
> This is to revert the core changes made by HDFS-8818. The reason is explained
> in the jira comments. HDFS-8818 put in config and logging changes that are
> tied to the core change. I will leave them as is.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
