Disabling a big table is a special operation since it has to flush
down a lot of data from memory (unless you didn't write to it) at the
same moment and that takes time. The first exception you pasted
normally indicates that the datanode is very busy. I suggest tail'ing
the region server logs to se
replying to myself here:
The exception I found was :
NativeException:
org.apache.hadoop.hbase.client.RegionOfflineException: region offline:
impressions_users,,1267133399076
Is there a way to 'force' disable/drop a table?
thanks
Sujee
http://sujee.net
On Thu, Feb 25, 2010 at 4:04 PM, Sujee
Hbase version : 0.20.3, r902334
EC2 c1.xlarge, 5 machine cluster (1 + 4
I have a couple of tables with 300M rows.
Truncate command hangs...
hbase shell> truncate 'tablename'
Truncating impressions_users; it may take a while
Disabling table...
< ^C at this point >
^CNativeException: java.io.IO
