[ 
https://issues.apache.org/jira/browse/HBASE-22049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jingyun Tian updated HBASE-22049:
---------------------------------
    Description: 
 

Now the split procedure is to unassign the split parent region, thus the state 
is CLOSED. And it only modify the regionInfo column during meta updating.

{code}

Put putParent = makePutFromRegionInfo(RegionInfoBuilder.newBuilder(parent)
 .setOffline(true)
 .setSplit(true).build(), time);

{code}

Thus if we want to recover the state from meta for a split parent region, its 
state is CLOSED instead of SPLIT. 

  was:
After we modify some attributes of table, hbaseAdmin will getAlterStatus to 
check if all region's attributes updated. It will skip opened region and split 
region as the following code shows.
{code}
    for (RegionState regionState: states) {
      if (!regionState.isOpened() && !regionState.isSplit()) {
        ritCount++;
      }
    }
{code}

But since now the split procedure is to unassign the split parent region, thus 
the state is CLOSED, and the check will hang there until timeout.


> RegionStateStore cannot recover SPLIT state from Meta for split parent region
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-22049
>                 URL: https://issues.apache.org/jira/browse/HBASE-22049
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jingyun Tian
>            Assignee: Jingyun Tian
>            Priority: Major
>         Attachments: HBASE-22049.master.004.patch
>
>
>  
> Now the split procedure is to unassign the split parent region, thus the 
> state is CLOSED. And it only modify the regionInfo column during meta 
> updating.
> {code}
> Put putParent = makePutFromRegionInfo(RegionInfoBuilder.newBuilder(parent)
>  .setOffline(true)
>  .setSplit(true).build(), time);
> {code}
> Thus if we want to recover the state from meta for a split parent region, its 
> state is CLOSED instead of SPLIT. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to