Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 63705 invoked from network); 5 May 2008 18:52:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 May 2008 18:52:21 -0000 Received: (qmail 69704 invoked by uid 500); 5 May 2008 18:52:20 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 69678 invoked by uid 500); 5 May 2008 18:52:20 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 69667 invoked by uid 99); 5 May 2008 18:52:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 May 2008 11:52:20 -0700 X-ASF-Spam-Status: No, hits=-1998.8 required=10.0 tests=ALL_TRUSTED,FS_REPLICA 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; Mon, 05 May 2008 18:51:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BBE9E234C114 for ; Mon, 5 May 2008 11:51:55 -0700 (PDT) Message-ID: <1964414690.1210013515768.JavaMail.jira@brutus> Date: Mon, 5 May 2008 11:51:55 -0700 (PDT) From: "lohit vijayarenu (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-3058) Hadoop DFS to report more replication metrics In-Reply-To: <1942260610.1205991864231.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594299#action_12594299 ] lohit vijayarenu commented on HADOOP-3058: ------------------------------------------ Yes, I also agree that these adds more operations. The metrics frequently updated are - filesTotal which are updated whenever we add/delete new files. - blocksTotal which are updated whenever we add/delete new blocks I guess it should be fine in the above case. Few metrics are replaced by updating a global variables regarding the DFS capacity. These were updated on each heart beat once, which should be fine. Another set of operations are done by ReplicationMonitor in ComputeDatanodeWork(), which should also be fine. > Hadoop DFS to report more replication metrics > --------------------------------------------- > > Key: HADOOP-3058 > URL: https://issues.apache.org/jira/browse/HADOOP-3058 > Project: Hadoop Core > Issue Type: Improvement > Components: dfs, metrics > Reporter: Marco Nicosia > Assignee: lohit vijayarenu > Priority: Minor > Attachments: HADOOP-3058-2.patch, HADOOP-3058.patch > > > Currently, the namenode and each datanode reports 'blocksreplicatedpersec.' > We'd like to be able to graph pending replications, vs number of under replicated blocks, vs. replications per second, so that we can get a better idea of the replication activity within the DFS. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.