Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8C2F119AB8 for ; Fri, 29 Apr 2016 18:37:07 +0000 (UTC) Received: (qmail 97665 invoked by uid 500); 29 Apr 2016 18:35:34 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 97628 invoked by uid 500); 29 Apr 2016 18:35:34 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 97609 invoked by uid 99); 29 Apr 2016 18:35:34 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Apr 2016 18:35:34 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id EE0A62C1F68 for ; Fri, 29 Apr 2016 18:35:12 +0000 (UTC) Date: Fri, 29 Apr 2016 18:35:12 +0000 (UTC) From: "Hudson (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-10335) Mover$Processor#chooseTarget() always chooses the first matching target storage group MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-10335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264503#comment-15264503 ] Hudson commented on HDFS-10335: ------------------------------- FAILURE: Integrated in Hadoop-trunk-Commit #9695 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/9695/]) HDFS-10335 Mover$Processor#chooseTarget() always chooses the first (szetszwo: rev 4da6f69ca129b28a5dad0a66d0c24e725ce25a3a) * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/mover/Mover.java > Mover$Processor#chooseTarget() always chooses the first matching target storage group > ------------------------------------------------------------------------------------- > > Key: HDFS-10335 > URL: https://issues.apache.org/jira/browse/HDFS-10335 > Project: Hadoop HDFS > Issue Type: Bug > Components: balancer & mover > Affects Versions: 2.8.0 > Reporter: Mingliang Liu > Assignee: Mingliang Liu > Priority: Critical > Fix For: 2.7.3 > > Attachments: HDFS-10335.000.patch, HDFS-10335.000.patch > > > Currently the {{org.apache.hadoop.hdfs.server.mover.Mover$Processor#chooseTarget()}} always chooses the first matching target datanode from the candidate list. This may make the mover schedule a lot of task to a few of the datanodes (first several datanodes of the candidate list). The overall performance will suffer significantly from this because of the saturated network/disk usage. Specially, if the {{dfs.datanode.balance.max.concurrent.moves}} is set, the scheduled move task will be queued on a few of the storage group, regardless of other available storage groups. We need an algorithm which can distribute the move tasks approximately even across all the candidate target storage groups. > Thanks [~szetszwo] for offline discussion. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org