[
https://issues.apache.org/jira/browse/HBASE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593488#action_12593488
]
stack commented on HBASE-478:
-----------------------------
I thought HBASE-609 also fixed this issue but I just tested with a 40 region
table and there are laggards... 3 regions that wouldn't offline. Then
enabling, only about 10 or 12 came back online. Deleting, all but the 3 that
wouldn't offline went away. Once it gets into the half-online/half-offline
state, its hosed (which is odd -- a second run of disable should just offline
whatever is still online).
> 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
> Reporter: stack
> Assignee: Jim Kellerman
> Priority: Critical
> Fix For: 0.2.0, 0.1.2
>
>
> 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.
