hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-845) HCM.isTableEnabled doesn't really tell if it is, or not
Date Thu, 29 Jan 2009 16:54:59 GMT

     [ https://issues.apache.org/jira/browse/HBASE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jean-Daniel Cryans updated HBASE-845:
-------------------------------------

    Fix Version/s: 0.20.0

Passes tests, committed to trunk. Should it also go into 0.19 branch since it improves an
important admin method?

> HCM.isTableEnabled doesn't really tell if it is, or not
> -------------------------------------------------------
>
>                 Key: HBASE-845
>                 URL: https://issues.apache.org/jira/browse/HBASE-845
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.20.0
>
>         Attachments: hbase-845-v2.patch, hbase-845.patch
>
>
> 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