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 632ED173E0 for ; Mon, 20 Apr 2015 10:13:59 +0000 (UTC) Received: (qmail 582 invoked by uid 500); 20 Apr 2015 10:13:59 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 520 invoked by uid 500); 20 Apr 2015 10:13:59 -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 508 invoked by uid 99); 20 Apr 2015 10:13:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Apr 2015 10:13:59 +0000 Date: Mon, 20 Apr 2015 10:13:59 +0000 (UTC) From: "Hadoop QA (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-8147) Mover should not select the DN storage as target where already same replica exists. 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-8147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502599#comment-14502599 ] Hadoop QA commented on HDFS-8147: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12726523/HDFS-8147_1.patch against trunk revision 8511d80. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:red}-1 findbugs{color}. The patch appears to introduce 4 new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/10314//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/10314//artifact/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/10314//console This message is automatically generated. > Mover should not select the DN storage as target where already same replica exists. > ----------------------------------------------------------------------------------- > > Key: HDFS-8147 > URL: https://issues.apache.org/jira/browse/HDFS-8147 > Project: Hadoop HDFS > Issue Type: Bug > Components: balancer & mover > Affects Versions: 2.6.0 > Reporter: surendra singh lilhore > Assignee: surendra singh lilhore > Attachments: HDFS-8147.patch, HDFS-8147_1.patch > > > *Scenario:* > 1. Three DN cluster. For DNs storage type is like this. > DN1 : DISK,ARCHIVE > DN2 : DISK > DN3 : DISK,ARCHIVE (All DNs are in same rack) > 2. One file with two replicas (In DN1 and DN2) > 3. Set file storage policy COLD > 4. Now execute Mover. > *Expected Result:* File blocks should move in DN1:ARCHIVE and DN3:ARCHIVE > *Actual Result:* {{chooseTargetInSameNode()}} move D1:DISK block to D1:ARCHIVE, but in next iteration {{chooseTarget()}} for same rake is selecting again DN1:ARCHIVE for target where already same block exists. > {{chooseTargetInSameNode()}} and {{chooseTarget()}} should not select the node as target where already same replica exists. > *Logs* > {code} > 15/04/15 10:47:17 WARN balancer.Dispatcher: Failed to move blk_1073741852_1028 with size=11990 from 10.19.92.74:50010:DISK to 10.19.92.73:50010:ARCHIVE through 10.19.92.73:50010: Got error, status message opReplaceBlock BP-1258709199-10.19.92.74-1428292615636:blk_1073741852_1028 received exception org.apache.hadoop.hdfs.server.datanode.ReplicaAlreadyExistsException: Replica FinalizedReplica, blk_1073741852_1028, FINALIZED > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)