Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 23176 invoked from network); 15 Dec 2009 01:41:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Dec 2009 01:41:40 -0000 Received: (qmail 72863 invoked by uid 500); 15 Dec 2009 01:41:40 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 72799 invoked by uid 500); 15 Dec 2009 01:41:40 -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 72789 invoked by uid 99); 15 Dec 2009 01:41:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 01:41:40 +0000 X-ASF-Spam-Status: No, hits=-10.0 required=5.0 tests=AWL,BAYES_00,FS_REPLICA,RCVD_IN_DNSWL_HI X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 01:41:38 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 17808234C498 for ; Mon, 14 Dec 2009 17:41:18 -0800 (PST) Message-ID: <124826428.1260841278081.JavaMail.jira@brutus> Date: Tue, 15 Dec 2009 01:41:18 +0000 (UTC) From: "Todd Lipcon (JIRA)" To: hdfs-issues@hadoop.apache.org Subject: [jira] Created: (HDFS-828) blocksWritten metric is double-incremented for blocks received via replication MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 blocksWritten metric is double-incremented for blocks received via replication ------------------------------------------------------------------------------ Key: HDFS-828 URL: https://issues.apache.org/jira/browse/HDFS-828 Project: Hadoop HDFS Issue Type: Bug Affects Versions: 0.22.0 Reporter: Todd Lipcon DataNode.closeBlock() takes care of incrementing the blocksWritten counter. However, BlockReceiver does this too when receiving from another DN. To test, I added log messages in both spots and ran TestReplication: 2009-12-14 17:38:10,656 WARN datanode.DataNode (BlockReceiver.java:receiveBlock(614)) - Incrementing counter in receiveBlock for block: blk_7127492210831810737_1001 in DN DataNode{data=FSDataset{dirpath='/home/todd/git/hadoop-hdfs/build/test/data/dfs/data/data15/current/finalized,/home/todd/git/hadoop-hdfs/build/test/data/dfs/data/data16/current/finalized'}, localName='127.0.0.1:54069', storageID='DS-896316964-127.0.1.1-54069-1260841088335', xmitsInProgress=0} 2009-12-14 17:38:10,656 WARN datanode.DataNode (DataNode.java:closeBlock(1289)) - Incrementing counter in closeBlock for block: blk_7127492210831810737_1001 in DN DataNode{data=FSDataset{dirpath='/home/todd/git/hadoop-hdfs/build/test/data/dfs/data/data15/current/finalized,/home/todd/git/hadoop-hdfs/build/test/data/dfs/data/data16/current/finalized'}, localName='127.0.0.1:54069', storageID='DS-896316964-127.0.1.1-54069-1260841088335', xmitsInProgress=0} (note that the block ID and DN are the same in both) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.