[ https://issues.apache.org/jira/browse/HDFS-14882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941748#comment-16941748 ]
Xiaoqiao He commented on HDFS-14882: ------------------------------------ [~lukmajercak], Thanks for your comments. This ticket is plan to adjust and sort location considering nodes' load whose distance to client is same. {quote}I only wish we could also use some sort of an estimate of load that we've already scheduled on each DN, not just xceivers reported by them.{quote} Sorry I don't understand that clearly. IIUC, we are also estimating load of node using its xceiver count when schedule write ops currently. Please correct me if i am wrong. Thanks. > 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 > > > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org