I was just testing 0.94.6RC1 and I forgot to install Snappy. Then I created a table with a CF that had Snappy enabled.
Now it is not possible to disable/drop this table. The master will abort when I try with the following: 2013-03-07 22:45:50,274 FATAL org.apache.hadoop.hbase.master.HMaster: Unexpected state : myTable,,1362725053267.784373d454f50d28427b1b5ff872c49f. state=PENDING_OPEN, ts=1362725150273, server=bunnypig,60020,1362725132107 .. Cannot transit it to OFFLINE. java.lang.IllegalStateException: Unexpected state : myTable,,1362725053267.784373d454f50d28427b1b5ff872c49f. state=PENDING_OPEN, ts=1362725150273, server=bunnypig,60020,1362725132107 .. Cannot transit it to OFFLINE. at org.apache.hadoop.hbase.master.AssignmentManager.setOfflineInZooKeeper(AssignmentManager.java:1813) at org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1658) at org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1423) at org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1398) at org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1393) at org.apache.hadoop.hbase.master.handler.ClosedRegionHandler.process(ClosedRegionHandler.java:105) I can swear that I disabled/dropped tables before without a problem when that (forgetting to install Snappy) happened. Is anybody aware of a change in the recent RC that could cause this? (not enough to sink the RC, but something - potentially - to track down) -- Lars
