Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 32853 invoked from network); 8 Apr 2011 17:58:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Apr 2011 17:58:50 -0000 Received: (qmail 1649 invoked by uid 500); 8 Apr 2011 17:58:47 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 1603 invoked by uid 500); 8 Apr 2011 17:58:47 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 1595 invoked by uid 99); 8 Apr 2011 17:58:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Apr 2011 17:58:47 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of qwertymaniac@gmail.com designates 209.85.161.48 as permitted sender) Received: from [209.85.161.48] (HELO mail-fx0-f48.google.com) (209.85.161.48) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Apr 2011 17:58:42 +0000 Received: by fxm7 with SMTP id 7so4156042fxm.35 for ; Fri, 08 Apr 2011 10:58:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type:content-transfer-encoding; bh=CB9Fyu6TY/nNA9fdKVFxXFcwvQuZU1TZiRkH+B0d+LY=; b=bL+64V7d0QfppXQTYaR3FkmMM1jZZFm7gnHD/vPc6R+lXNGe6w61StFHYSD3IwclHE n7LciT2lZRcgm07lZv3yEl5wDL4mqx1qjZnl3aPJUfZMLfZmDimsQzJ1SsHJhvYbEt9g FDBfMVuNT6oJaabVqPdezD4ezNi+imN3RNs3s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=NSSXvMwiXTP9d/FCtercBplLlDtP4aevY2s8cDbb2ENmiXCJqYrAc4Orq6/ogio+Um dkIBLhTTtjP1d8zhPabbI2RP7G9BR43g4dNAmLiC1X06CK4pUpfaVcKzlLYtJqjoAMVR y4lAss19whvMHSBUfIVwnaWDEJMOUSO4J7t6I= Received: by 10.223.95.138 with SMTP id d10mr2618844fan.21.1302285501468; Fri, 08 Apr 2011 10:58:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.87.214 with HTTP; Fri, 8 Apr 2011 10:58:01 -0700 (PDT) In-Reply-To: <58142C191905468D88BB56CB8AC060AC@RINGRING> References: <58142C191905468D88BB56CB8AC060AC@RINGRING> From: Harsh J Date: Fri, 8 Apr 2011 23:28:01 +0530 Message-ID: Subject: Re: Re:HDFS start-up with safe mode? To: common-user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello, I'm not quite clear why you'd want to disable a consistency check such as the safemode feature. It is to guarantee that your DFS is to be made ready only after it has sufficient blocks reported to start handling your dfs requests. If your NN ever goes into safemode later, it is vital that you take a look at logs and fsck reports to determine what's gone wrong. On Fri, Apr 8, 2011 at 3:06 PM, springring wrote: > I modify the value of "dfs.safemode.threshold.pct" to zero, now everythin= g is ok. > log file as below > But there are still three questions > > =A01.. Can I regain percentage of blocks that should satisfy the minimal = replication requirement > =A0 =A0 =A0 =A0 =A0to 99.9%? =A0hadoop balancer? For I feel it will be mo= re safe. The safemode is to guarantee that. That is why it is called the 'safe' mode. Not sure what you mean by the balancer thing. In production one never restarts the NameNode frequently, so I s'pose this is just to get rid of some development hassles? You may want to additionally lower the leave-safemode extension period from 30s to 0s to get rid of the check entirely, anyway. --=20 Harsh J http://harshj.com