[
https://issues.apache.org/jira/browse/HBASE-13326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379826#comment-14379826
]
Matteo Bertozzi commented on HBASE-13326:
-----------------------------------------
the checkstyle is for the longline, I can fix it on commit. if no other comments
{code}if (tableStateManager.isTableState(regionInfo.getTable(),
ZooKeeperProtos.Table.State.DISABLED)) {code}
> Disabled table can't be enabled after HBase is restarted
> --------------------------------------------------------
>
> Key: HBASE-13326
> URL: https://issues.apache.org/jira/browse/HBASE-13326
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.0.0, 1.1.0, 0.98.12
> Reporter: Dima Spivak
> Assignee: Andrey Stepachev
> Priority: Blocker
> Fix For: 1.0.1, 1.1.0, 0.98.12
>
> Attachments: HBASE-13326-0.98.patch, HBASE-13326-branch-1.0.patch,
> HBASE-13326-branch-1.0.patch, HBASE-13326-branch-1.0.v2.patch,
> HBASE-13326-branch-1.patch, HBASE-13326-branch-1.v2.patch
>
>
> The folks at Intel discovered a pretty nasty bug in 1.0 and 1.1 (but not
> master). Steps to reproduce:
> 1. Create a table, any table.
> 2. Disable the table.
> 3. Restart HBase.
> 4. Try enabling the table.
> The table won't become enabled and the master web UI will indicate a
> never-ending region in transition. Also worth noting is that [~mbertozzi] dug
> in and noted that this isn't happening in the master branch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
