[
https://issues.apache.org/jira/browse/HBASE-19915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349572#comment-16349572
]
Umesh Agashe commented on HBASE-19915:
--------------------------------------
{color:#333333}In case of merge, merged region has state null which is
interpreted as OFFLINE as noted in HBASE-19529.{color}
> From SplitTableRegionProcedure daughter regions get created in OFFLINE state
> ----------------------------------------------------------------------------
>
> Key: HBASE-19915
> URL: https://issues.apache.org/jira/browse/HBASE-19915
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.0.0-beta-1
> Reporter: Umesh Agashe
> Assignee: Umesh Agashe
> Priority: Major
> Fix For: 2.0.0-beta-2
>
>
> See HBASE-19530. When regions are created initial state should be CLOSED. Bug
> was discovered while debugging flaky test
> TestSplitTableRegionProcedure#testRollbackAndDoubleExecution with numOfSteps
> set to 4. After updating daughter regions in meta when master is restarted,
> startup sequence of master assigns all OFFLINE regions. As daughter regions
> are stored with OFFLINE state, daughter regions are assigned. This is
> followed by re-assignment of daughter regions from resumed
> SplitTableRegionProcedure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
