[
https://issues.apache.org/jira/browse/HBASE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594356#action_12594356
]
Jim Kellerman commented on HBASE-478:
-------------------------------------
I removed the table delete because enable/disable are asychronous and might not
be deterministic for a test case. Given that this table is so small, that may
not be an issue, on the other hand, it doesn't test much either since we
generally needed a table of 30-40 regions to get enable/disable to fail.
I can put back the table delete if you want, preceded by a disable. I don't
have a strong opinion either way. Your call.
> 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.
