hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nanheng Wu <nanhen...@gmail.com>
Subject Re: Disabling a table taking very long time
Date Thu, 17 Feb 2011 00:26:35 GMT
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 <jdcryans@apache.org> 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 <nanhengwu@gmail.com> 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!

View raw message