[
https://issues.apache.org/jira/browse/HBASE-19530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16293663#comment-16293663
]
Appy edited comment on HBASE-19530 at 12/16/17 5:26 AM:
--------------------------------------------------------
Btw, i predict that this patch might make "fix" TestTruncateTableProcedure.
I quote fix because, those failures are result of two assumption collectively
resulting in a failure (region state = null --> assume OFFLINE, table state =
null --> assume ENABLED).
This will break the first one and test might start passing.
But we still need to address the second one, and that will be done in
HBASE-19529.
was (Author: appy):
Btw, i predict that this patch might make "fix" TestTruncateTableProcedure.
I quote fix because, those failures are result of two assumption collectively
resulting in a failure (region state = null --> assume OFFLINE, table state =
null --> assume ENABLED).
This is break the first one of them and test might start passing.
But we still need to address the second one, and that will be done in
HBASE-19529.
> New regions should always be added with state CLOSED
> ----------------------------------------------------
>
> Key: HBASE-19530
> URL: https://issues.apache.org/jira/browse/HBASE-19530
> Project: HBase
> Issue Type: Bug
> Reporter: Appy
> Attachments: HBASE-19530.master.001.patch
>
>
> We shouldn't add regions with state null. In case of failures and recovery,
> it's not possible to determine what did it mean and things become uncertain.
> All operations should add regions in a well defined state.
> For now, we'll set the default to CLOSED, since whatever ops are adding new
> regions, they would anyways be enabling them explicitly if needed.
> fyi: [~stack]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
