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 "Xiaoqiao He (Jira)" <ji...@apache.org> on 2019/11/02 10:13:00 UTC
[jira] [Updated] (HDFS-14882) Consider DataNode load when
#getBlockLocation
[ https://issues.apache.org/jira/browse/HDFS-14882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoqiao He updated HDFS-14882:
-------------------------------
Attachment: HDFS-14882.010.patch
> Consider DataNode load when #getBlockLocation
> ---------------------------------------------
>
> Key: HDFS-14882
> URL: https://issues.apache.org/jira/browse/HDFS-14882
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Xiaoqiao He
> Assignee: Xiaoqiao He
> Priority: Major
> Attachments: HDFS-14882.001.patch, HDFS-14882.002.patch, HDFS-14882.003.patch, HDFS-14882.004.patch, HDFS-14882.005.patch, HDFS-14882.006.patch, HDFS-14882.007.patch, HDFS-14882.008.patch, HDFS-14882.009.patch, HDFS-14882.010.patch, HDFS-14882.suggestion
>
>
> Currently, we consider load of datanode when #chooseTarget for writer, however not consider it for reader. Thus, the process slot of datanode could be occupied by #BlockSender for reader, and disk/network will be busy workload, then meet some slow node exception. IIRC same case is reported times. Based on the fact, I propose to consider load for reader same as it did #chooseTarget for writer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org