hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bassam Tabbara (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1636) disable and drop of table is flakey still
Date Mon, 14 Dec 2009 21:32:18 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790384#action_12790384
] 

Bassam Tabbara commented on HBASE-1636:
---------------------------------------

One more data point. Restarting the master seems to have resolved the issue. The zombie regions
seem to have gone away. I wonder if the old .META. information is cached in memory somewhere.
Are they?

> disable and drop of table is flakey still
> -----------------------------------------
>
>                 Key: HBASE-1636
>                 URL: https://issues.apache.org/jira/browse/HBASE-1636
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>             Fix For: 0.21.0
>
>         Attachments: hbase-hbase-master-ip-10-212-65-235.log, hbase-hbase-regionserver-ip-10-212-66-112.log
>
>
> Just now, cheddar up on IRC had table of 2k regions.  A disable and drop gave him 2k
rows in meta of historian info.  He couldn't progress.  Had to make below script for him:
> {code}
> meta = HTable.new(".META.")
> historian = "historian:"
> scanner = meta.getScanner([historian].to_java(java.lang.String))
> while (result = scanner.next())
>       meta.deleteAll(result.getRow())
> end
> exit 0
> {code}
> This flakey disable/enable/drop is frustrating users.  Need to fix.

-- 
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