hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jieshan Bean (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5927) AM#unassign should handle local exceptions after calling sendRegionClose
Date Tue, 08 May 2012 15:11:50 GMT

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

Jieshan Bean updated HBASE-5927:
--------------------------------

    Attachment: TestCaseForReProduce.txt

A simple test just help for producing this issue.

The below logs show this problem:

Kill one RegionServer:
{noformat}
2012-05-08 22:04:03,038 INFO  [MASTER_SERVER_OPERATIONS-Jieshan.china.huawei.com,57110,1336485831968-0]
handler.ServerShutdownHandler(174): Splitting logs for Jieshan.china.huawei.com,57163,1336485834464
{noformat}
Local exception occured after calling sendRegionClose
{noformat}
2012-05-08 22:05:23,909 INFO  [Jieshan.china.huawei.com,57110,1336485831968-org.apache.hadoop.hbase.master.handler.DisableTableHandler$BulkDisabler-1]
master.AssignmentManager(2066): Server jieshan.china.huawei.com,57138,1336485834409 returned
java.net.ConnectException: Connection refused: no further information for fc6c3b7c6445127b63f617445aa5dfaf
{noformat}
Fallen into an end-less loop.
{noformat}
2012-05-08 22:07:58,122 INFO  [Jieshan.china.huawei.com,57110,1336485831968.timeoutMonitor]
master.AssignmentManager$TimeoutMonitor(2925): Region has been PENDING_CLOSE for too long,
running forced unassign again on region=testHBase5937,000,1336485845463.fc6c3b7c6445127b63f617445aa5dfaf.
2012-05-08 22:07:58,122 DEBUG [pool-8-thread-17] master.AssignmentManager(1936): Starting
unassignment of region testHBase5937,000,1336485845463.fc6c3b7c6445127b63f617445aa5dfaf. (offlining)
2012-05-08 22:07:58,122 DEBUG [pool-8-thread-17] master.AssignmentManager(1942): Attempted
to unassign region testHBase5937,000,1336485845463.fc6c3b7c6445127b63f617445aa5dfaf. but it
is not currently assigned anywhere
2012-05-08 22:08:08,121 INFO  [Jieshan.china.huawei.com,57110,1336485831968.timeoutMonitor]
master.AssignmentManager$TimeoutMonitor(2893): Regions in transition timed out:  testHBase5937,000,1336485845463.fc6c3b7c6445127b63f617445aa5dfaf.
state=PENDING_CLOSE, ts=1336485917495, server=null
2012-05-08 22:08:08,121 INFO  [Jieshan.china.huawei.com,57110,1336485831968.timeoutMonitor]
master.AssignmentManager$TimeoutMonitor(2925): Region has been PENDING_CLOSE for too long,
running forced unassign again on region=testHBase5937,000,1336485845463.fc6c3b7c6445127b63f617445aa5dfaf.
2012-05-08 22:08:08,121 DEBUG [pool-8-thread-13] master.AssignmentManager(1936): Starting
unassignment of region testHBase5937,000,1336485845463.fc6c3b7c6445127b63f617445aa5dfaf. (offlining)
2012-05-08 22:08:08,121 DEBUG [pool-8-thread-13] master.AssignmentManager(1942): Attempted
to unassign region testHBase5937,000,1336485845463.fc6c3b7c6445127b63f617445aa5dfaf. but it
is not currently assigned anywhere
2012-05-08 22:08:18,122 INFO  [Jieshan.china.huawei.com,57110,1336485831968.timeoutMonitor]
master.AssignmentManager$TimeoutMonitor(2893): Regions in transition timed out:  testHBase5937,000,1336485845463.fc6c3b7c6445127b63f617445aa5dfaf.
state=PENDING_CLOSE, ts=1336485917495, server=null
2012-05-08 22:08:18,122 INFO  [Jieshan.china.huawei.com,57110,1336485831968.timeoutMonitor]
master.AssignmentManager$TimeoutMonitor(2925): Region has been PENDING_CLOSE for too long,
running forced unassign again on region=testHBase5937,000,1336485845463.fc6c3b7c6445127b63f617445aa5dfaf.
2012-05-08 22:08:18,122 DEBUG [pool-8-thread-6] master.AssignmentManager(1936): Starting unassignment
of region testHBase5937,000,1336485845463.fc6c3b7c6445127b63f617445aa5dfaf. (offlining)
2012-05-08 22:08:18,125 DEBUG [pool-8-thread-6] master.AssignmentManager(1942): Attempted
to unassign region testHBase5937,000,1336485845463.fc6c3b7c6445127b63f617445aa5dfaf. but it
is not currently assigned anywhere
{noformat}
                
> AM#unassign should handle local exceptions after calling sendRegionClose
> ------------------------------------------------------------------------
>
>                 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: 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