Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BF61711829 for ; Wed, 20 Aug 2014 15:17:16 +0000 (UTC) Received: (qmail 28720 invoked by uid 500); 20 Aug 2014 15:17:10 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 28645 invoked by uid 500); 20 Aug 2014 15:17:10 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 28627 invoked by uid 99); 20 Aug 2014 15:17:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Aug 2014 15:17:10 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.220.175] (HELO mail-vc0-f175.google.com) (209.85.220.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Aug 2014 15:17:05 +0000 Received: by mail-vc0-f175.google.com with SMTP id ik5so9182220vcb.20 for ; Wed, 20 Aug 2014 08:16:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=rSmiJHxm2Pn2Eeuix0hR4J4s/wZi3UeJePw6oFiIc64=; b=BIOf4tpYF5OKqvFo6Q/dJo72GLC0XLyqUOrzWiCsqApvXTihtmvQUxtI2/BMLnoZUz jpdwFmufWioxL7yhpO/NamjMYBP4d+nfWxS9G87m2373bTGAdeEvOv996ImbTX4OagPB LlO7toAxnsKFwteb9vqLx7hYrh3OSBe4eBQx53jOsNDgsiVRCjbQ1/hHpKzKL5Xfegqd nG3ygbbln1QRcYlzFvx82qtIA1xgGh3tkQjyR2LaFZ6JFvvQXhMyCeLjxjQdtqxe9h7S MKKm3sT4ap3hEX0BRDwUncEna/oftF16iU1owxbs9Y2LrRh4YyQ7FRRo1pNNQ+U0Mnew bvKw== X-Gm-Message-State: ALoCoQnkqCtqSQGinBpBuVI/1C+Rt8/ktsJx4btSrVMp1xVKSVoTLoulYTrYn4sVvmN5uYcz9Hsj X-Received: by 10.52.136.196 with SMTP id qc4mr14814909vdb.22.1408547804896; Wed, 20 Aug 2014 08:16:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.113.1 with HTTP; Wed, 20 Aug 2014 08:16:24 -0700 (PDT) In-Reply-To: <53F4BAC9.70803@zfabrik.de> References: <53F4B0CB.50701@zfabrik.de> <53F4BAC9.70803@zfabrik.de> From: Jean-Marc Spaggiari Date: Wed, 20 Aug 2014 11:16:24 -0400 Message-ID: Subject: Re: delete ".corrupt" folder? To: user Content-Type: multipart/alternative; boundary=bcaec51b12bd8fa33b05011117da X-Virus-Checked: Checked by ClamAV on apache.org --bcaec51b12bd8fa33b05011117da Content-Type: text/plain; charset=UTF-8 They seems to be the logs as said before. But as you said too, too late now ;) We can not take one and look at it. Basically, when you ran out of space, mot probably HBase failed to write the logs correctly so the files got corrupted, and got moved into this folder when they got replayed. Since it's a standalone instance I guess it's not production so this is not a big issue. JM 2014-08-20 11:12 GMT-04:00 Henning Blohm : > Ah.. man.. sorry for the confusion: Just noted that the terminal was still > open. Here's the output from the delete: > > $ hadoop fs -rmr /hbase/.corrupt/* > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1406915392963 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1407034197420 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1407246602219 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1407770546240 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1407773074652 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1407773969678 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408241347935 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408241348470 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408241348677 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408241349446 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408241349732 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408241350291 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408241350733 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408241351260 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408241351469 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408244952906 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408450158299 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408450158313 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408477692983 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408481294207 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408481294227 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408481294237 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408481294245 > Deleted hdfs://localhost:9000/hbase/.corrupt/localhost%3A60020. > 1408481294257 > > Does that say anything to you? > > > Thanks, > Henning > > On 08/20/2014 04:43 PM, Jean-Marc Spaggiari wrote: > >> Can you list the files you have under this directory? >> >> Look at 9.6.5.3.1 in http://hbase.apache.org/book/regionserver.arch.html >> >> They might be corrupt logs files that we can not replay. So might be safe >> to remove, but you might have some data lost there... >> >> JM >> >> >> >> 2014-08-20 10:29 GMT-04:00 Henning Blohm : >> >> Nobody? >>> >>> Well... I will try and see what happens... >>> >>> Thanks, >>> Henning >>> >>> >>> On 08/11/2014 09:28 PM, Henning Blohm wrote: >>> >>> Lately, on a single node test installation, I noticed that the >>>> Hadoop/Hbase folder /hbase/.corrupt got quite big (probably due to >>>> failed >>>> log splitting due to lack of disk space). >>>> >>>> Is it safe to simply delete that folder? >>>> >>>> And, what would one possibly do with those problematic WAL logs? >>>> >>>> Thanks, >>>> Henning >>>> >>>> >>> > --bcaec51b12bd8fa33b05011117da--