hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "rajeshbabu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5927) SSH and DisableTableHandler happening together does not clear the znode of the region and RIT map.
Date Wed, 16 May 2012 08:53:03 GMT

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

rajeshbabu commented on HBASE-5927:
-----------------------------------


bq.2.For the disabling table regions, ServerShutdownHandler will assign it with HBASE-5914,
however, OpenedRegionHandler will unassign it again after it is opened.

unassign happen only when znode deletion failed in OpenedRegionHandler
{code}
      openedNodeDeleted = deleteOpenedNode(expectedVersion);
{code}
if znode deleted success fully we end up with assignment of disabling table regions because
we cannot call unassign in this case.
                
> SSH and DisableTableHandler happening together does not clear the znode of the region
and RIT map.
> --------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5927
>                 URL: https://issues.apache.org/jira/browse/HBASE-5927
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.92.1, 0.96.0, 0.94.1
>            Reporter: Jieshan Bean
>            Assignee: Jieshan Bean
>             Fix For: 0.92.2, 0.96.0, 0.94.1
>
>         Attachments: HBASE-5927_94.patch, HBASE-5927_94_v2.patch, HBASE-5927_trunk.patch,
HBASE-5927_trunk_2.patch, TestCaseForReProduce.txt
>
>
> A possible exception: If the related regionserver was just killed(But HMaster has not
perceived that), then we will get a local exception "Connection reset by peer". If this region
belongs to a disabling table. what will happen?
> ServerShutdownHandler will remove this region from AM#regions. So this region is still
existing in RIT. TimeoutMonitor will take care of it after it got timeout. Then invoke unassign
again. Since this region has been removed from AM#regions, it will return directly due to
the below code:
> {code}
>     synchronized (this.regions) {
>       // Check if this region is currently assigned
>       if (!regions.containsKey(region)) {
>         LOG.debug("Attempted to unassign region " +
>           region.getRegionNameAsString() + " but it is not " +
>           "currently assigned anywhere");
>         return;
>       }
>     }
> {code}
> Then it leads to an end-less loop.

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

        

Mime
View raw message