hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Feng Honghua (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-10662) RegionScanner should be closed and according lease should be cancelled in regionserver immediately if we find the related region has been re-opened during performing scan request
Date Tue, 04 Mar 2014 09:08:20 GMT

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

Feng Honghua updated HBASE-10662:
---------------------------------

    Summary: RegionScanner should be closed and according lease should be cancelled in regionserver
immediately if we find the related region has been re-opened during performing scan request
 (was: RegionScanner should be closed and according lease should be cancelled in regionserver
immediately if the related region has been re-opened during performing scan request)

> RegionScanner should be closed and according lease should be cancelled in regionserver
immediately if we find the related region has been re-opened during performing scan request
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-10662
>                 URL: https://issues.apache.org/jira/browse/HBASE-10662
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>            Reporter: Feng Honghua
>            Assignee: Feng Honghua
>         Attachments: HBASE-10662-trunk_v1.patch
>
>
> During regionserver processes scan request from client, it fails the request by throwing
a wrapped NotServingRegionException to client if it finds the region related to the passed-in
scanner-id has been re-opened, and it also removes the RegionScannerHolder from the scanners.
In fact under this case, the old and invalid RegionScanner related to the passed-in scanner-id
should be closed and the related lease should be cancelled at the mean time as well.
> Currently region's related scanners aren't closed when closing the region, a region scanner
is closed only when requested explicitly by client, or by expiration of the related lease,
in this sense the close of region scanners is quite passive and lag.
> Sounds reasonable to cleanup all related scanners and cancel these scanners' leases after
closing a region?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message