Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 85108 invoked from network); 11 Feb 2009 18:18:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Feb 2009 18:18:42 -0000 Received: (qmail 54973 invoked by uid 500); 11 Feb 2009 18:18:40 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 54703 invoked by uid 500); 11 Feb 2009 18:18:39 -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 54691 invoked by uid 99); 11 Feb 2009 18:18:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Feb 2009 10:18:39 -0800 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=FS_REPLICA,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [69.147.107.20] (HELO mrout1-b.corp.re1.yahoo.com) (69.147.107.20) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Feb 2009 18:18:29 +0000 Received: from SNV-EXBH01.ds.corp.yahoo.com (snv-exbh01.ds.corp.yahoo.com [207.126.227.249]) by mrout1-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id n1BIG2Bh065130 for ; Wed, 11 Feb 2009 10:16:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:user-agent:date:subject:from:to:message-id: thread-topic:thread-index:in-reply-to:mime-version:content-type: content-transfer-encoding:return-path:x-originalarrivaltime; b=QEFWWJi1Yf6PmgymFfWWhoVyiO2htMYZKFjvssK90JXzQt0AeC44s9I1kKRlDXy5 Received: from SNV-EXVS09.ds.corp.yahoo.com ([207.126.227.87]) by SNV-EXBH01.ds.corp.yahoo.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 11 Feb 2009 10:16:21 -0800 Received: from 10.72.112.100 ([10.72.112.100]) by SNV-EXVS09.ds.corp.yahoo.com ([207.126.227.84]) via Exchange Front-End Server snv-webmail.corp.yahoo.com ([207.126.227.59]) with Microsoft Exchange Server HTTP-DAV ; Wed, 11 Feb 2009 18:16:21 +0000 User-Agent: Microsoft-Entourage/12.15.0.081119 Date: Wed, 11 Feb 2009 10:16:20 -0800 Subject: Re: adding replication status to dfshealth.jsp From: Hairong Kuang To: hadoop-dev Message-ID: Thread-Topic: adding replication status to dfshealth.jsp Thread-Index: AcmMdNaGnNbsBSFZLU6RCAQYldcYHQ== In-Reply-To: <3b5f72030902110918v730992c0o828ad90757a942b2@mail.gmail.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 11 Feb 2009 18:16:21.0632 (UTC) FILETIME=[D77F7800:01C98C74] X-Virus-Checked: Checked by ClamAV on apache.org It's available in 0.18. Remember that the file is saved at NameNode side. It took me a while for me to figure out where the file was the first time I used this tool. Hairong On 2/11/09 9:18 AM, "Bill Au" wrote: > Thanks for the info. What version(s) is "-metaSave" available for? I am > running 0.18.2 and it doesn't work there. > > Bill > > On Tue, Feb 10, 2009 at 9:04 PM, Raghu Angadi wrote: > >> >> one more thing I forgot : >> >> Another useful tool is 'bin/hadoop dfsadmin -metaSave' >> >> This lists all the blocks that are under replicated. This is not very >> official and not used much. It needs to be more user friendly (currently it >> writes to a file on the NameNode)... I might improve (and/or rename) it as a >> follow up to HADOOP-4103. >> >> Stats like dfs.FSNamesystem.UnderReplicatedBlocks that Brain mentioned are >> useful to find if there is some problem. And the commands like the one above >> help in finding which specific blocks are in these states. >> >> Raghu. >> >> >> >> Bill Au wrote: >> >>> I am in the process of setting up remote monitoring of my Hadoop cluster. >>> I >>> seems to me that the replication status can only be obtained from the >>> command line by the fsck command. Has anyone though about adding >>> replication status to the NameNode web UI in dfshealth.jsp? Or is that >>> something that I really shouldn't worry about since Hadoop will fix things >>> all by itself? >>> >>> Bill >>> >>> >>