Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 50493 invoked from network); 31 Aug 2010 18:52:23 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 31 Aug 2010 18:52:23 -0000 Received: (qmail 98564 invoked by uid 500); 31 Aug 2010 18:52:22 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 98531 invoked by uid 500); 31 Aug 2010 18:52:22 -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 98523 invoked by uid 99); 31 Aug 2010 18:52:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Aug 2010 18:52:22 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates 74.125.82.51 as permitted sender) Received: from [74.125.82.51] (HELO mail-ww0-f51.google.com) (74.125.82.51) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Aug 2010 18:52:14 +0000 Received: by wwb39 with SMTP id 39so569483wwb.20 for ; Tue, 31 Aug 2010 11:51:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=WPEbJUZBatY/jkp6tZgHJs228XkAL/vCnZbhABi0fME=; b=mOMNGxbNcL2DWgpga2naF6aC8z/ScA1QTJz/TJokLdJdzD4k9u6ty/VaFJ6v1fdE/M NI/oyJRh2/JZmqamgGFdQD3BbuBQ7hadmjRietsUG0BUeV4asDqNyEGxSV1Xpi2f3imG HaoM7EbYynulsc8Q5DIUT38MMXwK7gDn6Mhg0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=hLDYXXzavtLtVfTV8Sc1ZYL4PbC5UQxxGbMV9EdCZaXnj0/eKk14RwjxFChuirlMSr GIp+3euO4O6Si5VZV5a3Ccl67M1pKbWZ+MEE9+oqoCc5mOR+fSZovwZn9FvR/IPB0Be7 Kfg386g0bQ+0kdTLpw43AlOmIDoeFpHX2V+bE= MIME-Version: 1.0 Received: by 10.227.131.68 with SMTP id w4mr5823177wbs.225.1283280713746; Tue, 31 Aug 2010 11:51:53 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.216.131.24 with HTTP; Tue, 31 Aug 2010 11:51:53 -0700 (PDT) In-Reply-To: References: Date: Tue, 31 Aug 2010 11:51:53 -0700 X-Google-Sender-Auth: cpuSYfTh0qEIavsf0aIEIxTOjDU Message-ID: Subject: Re: HBase table lost on upgrade From: Stack To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Aug 31, 2010 at 11:36 AM, Sharma, Avani wrote: > I just upgraded my 3-node cluster for 0.20.3 to 0.20.6. After I did this, I notice that some of my tables are missing. I recovered the lost tables using > add_table.rb. > > But I am starting to have doubts about the stability of Hbase now since I have had to recover lost tables a number of times now. What is the possible reason that the tables could have gone missing? > HBase can lose data if you you run with its defaults which put data into /tmp -- and then your machines are rebooted. HBase can lose data if you crash out your regionservers or kill -9 them -- use one of the 0.89 series releases and hadoop 0.20-append if you want hbase to preserve data across regionserver crashes. You seem to be having a bit of a tough time coming up to speed on hbase going by your recent mails to the list. HBase is not the easiest system to learn. It takes a bit of effort (We're working on making it easier to get going but are not there yet). If you want to take the time to keep track of what you are doing so you can replay it here on the list, we'll help you out. Do take the time to go over the 'getting started' documentation first though. Thanks, St.Ack