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

Zhihong Yu commented on HBASE-5165:
-----------------------------------

Patch looks interesting.

Have you verified that the patch fixes the problem ?
{code}
      LOG.debug("Waiting on processing of deadserver or initiallizing of 
master, deadServersInProgress = "
{code}
The above log should be removed. At least, its frequency should be reduced.
{code}
    if (masterServices.getServerManager().areDeadServersInProgress()
        || ((HMaster) server).isInitialized()) {
{code}
I think the above should be:
{code}
    if (masterServices.getServerManager().areDeadServersInProgress()
        || !((HMaster) server).isInitialized()) {
{code}
                
> Concurrent processing of DeleteTableHandler and ServerShutdownHandler may 
> cause deleted region to assign again
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5165
>                 URL: https://issues.apache.org/jira/browse/HBASE-5165
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.4
>            Reporter: chunhui shen
>         Attachments: hbase-5165.patch
>
>
> Concurrent processing of DeleteTableHandler and ServerShutdownHandler may 
> cause following situation
> 1.Table has already be disabled.
> 2.ServerShutdownHandler is doing MetaReader.getServerUserRegions.
> 3.When step2 is processing or is completed just now, DeleteTableHandler 
> starts to delete region(Remove region from META and Delete region from FS)
> 4.DeleteTableHandler set table enabled.
> 4.ServerShutdownHandler is starting to assign region which is alread deleted 
> by DeleteTableHandler.
> The result of above operations is producing an invalid record in .META.  and 
> can't be fixed by hbck 

--
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