[ 
https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395460#comment-13395460
 ] 

chunhui shen commented on HBASE-6227:
-------------------------------------

@ram
Let me describe it in more detail.

Suppose there are two regionservers A1 and B1, A1 carried META and ROOT

1.master restart and completed assignRootAndMeta

2.A1 and B1 are both restarted, new regionservers are A2 and B2

3.SSH which processed for A1 completed assigning ROOT and META

4.master do rebuilding user regions and no regions added to master's region list

5.master consider it as a cluster startup, and assign all user regions

6.SSH which processed for B1 start to split B1's logs

7.All regions' data carried by B1 would loss.
                
> SSH and cluster startup  causes data loss
> -----------------------------------------
>
>                 Key: HBASE-6227
>                 URL: https://issues.apache.org/jira/browse/HBASE-6227
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>         Attachments: HBASE-6227.patch
>
>
> In AssignmentManager#processDeadServersAndRegionsInTransition, if 
> servershutdownhandler is processing and master consider it cluster startup, 
> master will assign all user regions, however, servershutdownhandler has not 
> completed splitting logs.
> Detail process as the following( 1 master, 1 regionserver):
> 1.All the servers are killed
> 2.master start up, regionserver's zk node exists, so master will record it
> 3.master won't split any logs
> 4.regionserver start up, and master assign root and meta
> 5.the old regionserver is in SSH now, when rebuild user region, no region is 
> added in master's region list
> 6.master consider it is cluster up, so it will assign all user regions
> 7.However, some region's data is in logs which are splittting by SSH

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to