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 see exactly what's going on while trying to disable.
The fact that you were able to disable it afterwards indicates that the first disable call (inside truncate) eventually did it's thing. Where's the RegionOfflineException coming from? J-D On Fri, Feb 26, 2010 at 2:54 PM, Sujee Maniyam <su...@sujee.net> wrote: > 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 Maniyam <su...@sujee.net> wrote: >> 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.IOException: Call to /10.215.131.223:60000 >> failed on local exception: java.io.InterruptedIOException: Interruped >> while waiting for IO on channel >> java.nio.channels.SocketChannel[connected local=/10.215.131.223:36878 >> remote=/10.215.131.223:60000]. 28990 millis timeout left >> >> on the other hand, >> > disable 'table' >> > drop 'table' >> >> works just fine within seconds. >> >> >> Any one else have experienced this problem? Any specifics I should >> look for in the logs? >> >> thanks >> Sujee >> http://sujee.net >> >
