hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Created: (HBASE-845) disable then drop table is messy when table is > 4 or 5 M rows
Date Tue, 26 Aug 2008 04:39:44 GMT
disable then drop table is messy when table is > 4 or 5 M rows
--------------------------------------------------------------

                 Key: HBASE-845
                 URL: https://issues.apache.org/jira/browse/HBASE-845
             Project: Hadoop HBase
          Issue Type: Bug
            Reporter: stack


In current trunk, if i load a table of 8M rows and then try and delete it, the disable returns
saying the table was successfully deleted but when I then try to drop the table, it says table
not disabled.  I run the disable/drop cycle a few more times and still fails.  Eventually,
if I wait long enough, it succeeds.   Maybe the table drop should just block if table is seen
to have disabled regions in it.  As is, its a little disorientating the way it works.  Could
lead admins to distrust status messages emitted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message