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 9BE0E906C for ; Wed, 28 Mar 2012 05:08:51 +0000 (UTC) Received: (qmail 40406 invoked by uid 500); 28 Mar 2012 05:08:51 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 40065 invoked by uid 500); 28 Mar 2012 05:08:48 -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 39737 invoked by uid 99); 28 Mar 2012 05:08:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Mar 2012 05:08:46 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Mar 2012 05:08:44 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 2E5B1349CB0 for ; Wed, 28 Mar 2012 05:08:23 +0000 (UTC) Date: Wed, 28 Mar 2012 05:08:23 +0000 (UTC) From: "J.Andreina (Commented) (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1356038956.26919.1332911303252.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1838326097.36403.1332252939627.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-3119) Overreplicated block is not deleted even after the replication factor is reduced after sync follwed by closing that file 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-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240174#comment-13240174 ] J.Andreina commented on HDFS-3119: ---------------------------------- Hi, Even after the datanode has sent the block report many times, the overreplicated block is not deleted. Even if i execute fsck for that particular file after sometime the block remains overreplicated. > Overreplicated block is not deleted even after the replication factor is reduced after sync follwed by closing that file > ------------------------------------------------------------------------------------------------------------------------ > > Key: HDFS-3119 > URL: https://issues.apache.org/jira/browse/HDFS-3119 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node > Affects Versions: 0.24.0 > Reporter: J.Andreina > Priority: Minor > Fix For: 0.24.0, 0.23.2 > > > cluster setup: > -------------- > 1NN,2 DN,replication factor 2,block report interval 3sec ,block size-256MB > step1: write a file "filewrite.txt" of size 90bytes with sync(not closed) > step2: change the replication factor to 1 using the command: "./hdfs dfs -setrep 1 /filewrite.txt" > step3: close the file > * At the NN side the file "Decreasing replication from 2 to 1 for /filewrite.txt" , logs has occured but the overreplicated blocks are not deleted even after the block report is sent from DN > * while listing the file in the console using "./hdfs dfs -ls " the replication factor for that file is mentioned as 1 > * In fsck report for that files displays that the file is replicated to 2 datanodes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira