[
https://issues.apache.org/jira/browse/HBASE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594391#action_12594391
]
stack commented on HBASE-478:
-----------------------------
+1 on this patch.
I tested with a big table. I was able to disable, then enable, and then scan
the whole thing. I then did a remove and all regions were cleared from the
.META. (dropping a table that has not been first disabled comes back with
success though nothing happened but this is a HQL bug and HQL is going bye-byes
so not a worry). Its not removing the table directory but thats another issue.
Regards tests for enable/disable, maybe add them to TRUNK if can figure an easy
means of making assertions (Scan of .META. and all regions are on or offline?)
otherwise, lets worry about it next time we break this facility (smile). Lets
not tests get in way of adding this patch to branch.
> offlining of table does not run reliably
> ----------------------------------------
>
> Key: HBASE-478
> URL: https://issues.apache.org/jira/browse/HBASE-478
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.2.0, 0.1.2, 0.1.1
> Reporter: stack
> Assignee: Jim Kellerman
> Priority: Critical
> Fix For: 0.1.2
>
> Attachments: 478-0.1-v2.patch, 478-0.1.patch
>
>
> I have a table of 4 regions made w/ PE. I cannot reliably offline it. I'm
> using 'disable TestTable' and have traced it to ensure its not a problem in
> hql. What I see is that one region will get the offlined mark or maybe
> two.. but never all.
> Jim in IRC suggested that if we did the .TABLE. catalog table, offlining the
> entry there might be more reliable than trying to offline all regions in a
> table.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
