Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 41673 invoked from network); 17 Feb 2011 00:27:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Feb 2011 00:27:06 -0000 Received: (qmail 15595 invoked by uid 500); 17 Feb 2011 00:27:05 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 15542 invoked by uid 500); 17 Feb 2011 00:27:05 -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 15534 invoked by uid 99); 17 Feb 2011 00:27:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 00:27:04 +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 (nike.apache.org: domain of nanhengwu@gmail.com designates 209.85.160.41 as permitted sender) Received: from [209.85.160.41] (HELO mail-pw0-f41.google.com) (209.85.160.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 00:26:57 +0000 Received: by pwj8 with SMTP id 8so409511pwj.14 for ; Wed, 16 Feb 2011 16:26:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=OeDjJZ3cbV9ZhEU623U/D3kBcSg/28cay67rrvSDecU=; b=Vifgtu7+wLmdczKFqkLdxbEHx5QJRDI50BwxUjirXXxkVvshyGG2zfireVmwsQ8mS+ 8ZbystpsKP7gkOtPyhr5wmedFZfcOMAmF5WZ4dA6RdKsq/cEcjmn6lLix4SyUr9Zlj5d 4T4kzeGPAOkVN9XPUArmtmXMDm1XxdVoFN2vQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=syjlXSNXpHDZCKGxq+k/ciK8tmm8Yfygo6tJqn93wZm1+v0vI+eFWtb+sfl3PSda+T lRdBMTdSIZ2PDU0rLGIhajBv71wTPi9nxwC1m2/UzBq9vWjbvosg27jgvFjD0ewyoOz4 rC7E5atRWPwoDkCKVQM6BrefSkN8dCoBuNZDQ= MIME-Version: 1.0 Received: by 10.142.43.20 with SMTP id q20mr994806wfq.23.1297902395509; Wed, 16 Feb 2011 16:26:35 -0800 (PST) Received: by 10.142.234.2 with HTTP; Wed, 16 Feb 2011 16:26:35 -0800 (PST) In-Reply-To: References: Date: Wed, 16 Feb 2011 16:26:35 -0800 Message-ID: Subject: Re: Disabling a table taking very long time From: Nanheng Wu To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Actually I wanted to disable the table so I can drop it. It would be nice to be able to disable the table without flushing memstore. It's not possible in 0.20.6 is it? On Wed, Feb 16, 2011 at 2:30 PM, Jean-Daniel Cryans wrote: > To disable a region, it's memstore must first be flushed. That's done > sequentially for all regions that must be disabled inside a table. > There's not really a way around it unless you don't need that data. > > If you're planning to disable a table but at the same time need it to > be unavailable for the shortest time possible, I recommend calling a > flush on the table from the shell first and then some time later doing > the disable. How much later you ask? Well there's currently no easy > way to tell, I usually just tail any region server log file until I > see they're done. > > J-D > > On Wed, Feb 16, 2011 at 2:21 PM, Nanheng Wu wrote: >> From time to time I run into issues where disabling a table pretty >> much hangs. I am simply calling the disableTable method fo HBaseAdmin. >> The table has ~ 500 regions with default region file size. I couldn't >> tell anything abnormal from the master's log. When I click on the >> region from Master's web UI I get the "RegionOfflineException". I am >> using HBase 0.20.6 + Hadoop 0.20.2. My cluster has ~10 nodes with one >> node running Master/ZK/NameNode. Can someone help me understand what's >> wrong? Thanks! >> >