Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E078B10128 for ; Thu, 29 May 2014 03:23:33 +0000 (UTC) Received: (qmail 19269 invoked by uid 500); 29 May 2014 03:23:28 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 19134 invoked by uid 500); 29 May 2014 03:23:28 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 19122 invoked by uid 99); 29 May 2014 03:23:28 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 May 2014 03:23:28 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gsmsteve@gmail.com designates 209.85.220.180 as permitted sender) Received: from [209.85.220.180] (HELO mail-vc0-f180.google.com) (209.85.220.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 May 2014 03:23:24 +0000 Received: by mail-vc0-f180.google.com with SMTP id hy4so13499481vcb.11 for ; Wed, 28 May 2014 20:23:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=0Fbq48Z785DcLlMZYNbfL/rBjkehVDdlwZowl3OMlhc=; b=Z8jLGgYkQw4Y4uDImgFaR8L8RNtvammJLhgYv+mkvCzwVsJYI9fvU3x2lXhk7hXY0E KjBgNdU+cOQn1T+ZfaSrn1liiN1zGFusbWWIGXj/QI1p/Q4+LrI/LLoeh2GaICsEP1hg ruD9HiaYCWwtuOzpaWsXHWEYbmtQld2YKgclWIyw0jDs+DZQ7we2us5b8j7/9k2JMBcD C9zvTZiD3TlnB7IsOHROUzNF090gADWWIy8myE70ZFR918RftXE47QKUY2j7qPMqi5hY O6UOp0NuvRGT4nSj0i9gMmFV+Cbw5gp+EP4wclzWW7lIRxVGYUWsOVatTrId97m6+HhB +trw== X-Received: by 10.220.103.141 with SMTP id k13mr3929819vco.25.1401333780749; Wed, 28 May 2014 20:23:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.219.7 with HTTP; Wed, 28 May 2014 20:22:40 -0700 (PDT) In-Reply-To: References: From: Shumin Guo Date: Wed, 28 May 2014 22:22:40 -0500 Message-ID: Subject: Re: how to save dead node when it's disk is full? To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7b342d3036a4d204fa81722d X-Virus-Checked: Checked by ClamAV on apache.org --047d7b342d3036a4d204fa81722d Content-Type: text/plain; charset=UTF-8 If the datanode is dead, block replications will be re-replicated on other datanodes automatically. So, after a while, when those blocks have been re-replicated, you should be able to delete the data on the dead nodes and restart it. Here, I am assuming your cluster have enough space on other live nodes for the block replications. On Wed, May 28, 2014 at 7:34 PM, ch huang wrote: > hi,maillist: > one of my datanode is full ,so dead in cluster ,how can i > do to let it live again? > --047d7b342d3036a4d204fa81722d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
If the datanode is dead, block replications will be re-rep= licated on other datanodes automatically. So, after a while, when those blo= cks have been re-replicated, you should be able to delete the data on the d= ead nodes and restart it. Here, I am assuming your cluster have enough spac= e on other live nodes for the block replications.=C2=A0


On Wed, May 2= 8, 2014 at 7:34 PM, ch huang <justlooks@gmail.com> wrote:<= br>
hi,maillist:
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 one of my datanode is full ,so dead in cluster = ,how can i do to let it live again?

--047d7b342d3036a4d204fa81722d--