You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/02/01 23:48:00 UTC
[jira] [Commented] (HBASE-19915) From SplitTableRegionProcedure
daughter regions get created in OFFLINE state
[ https://issues.apache.org/jira/browse/HBASE-19915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349518#comment-16349518 ]
stack commented on HBASE-19915:
-------------------------------
Good one [~uagashe]... What about Merge? Do we create the Merge target in CLOSED state?
> 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 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)