[
https://issues.apache.org/jira/browse/HBASE-28396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881660#comment-17881660
]
Hudson commented on HBASE-28396:
--------------------------------
Results for branch master
[build #1162 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1162/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1162/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1162/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Quota throttling can cause a leak of scanners
> ---------------------------------------------
>
> Key: HBASE-28396
> URL: https://issues.apache.org/jira/browse/HBASE-28396
> Project: HBase
> Issue Type: Bug
> Reporter: Bryan Beaudreault
> Assignee: Hernan Gelaf-Romer
> Priority: Major
> Labels: pull-request-available
>
> In RSRpcServices.scan, we check the quota after having created a new
> RegionScannerHolder. If the quota is exceeded, an exception will be thrown.
> In this case, we can't send the scannerName back to the client because it's
> just an exception. So the client will be forced to retry the openScanner
> call, but the RegionScannerHolder is not closed. Eventually the scanners will
> be cleaned up by the lease expiration, but this could cause many scanners to
> leak during periods of high throttling.
> We could close the newly opened scanner before throwing the throttle
> exception, but I think it's better to not open the scanner at all until we've
> grabbed some quota.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
