[
https://issues.apache.org/jira/browse/HBASE-28716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867548#comment-17867548
]
Hudson commented on HBASE-28716:
--------------------------------
Results for branch master
[build #1126 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1126/]:
(x) *{color:red}-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/1126/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1126/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1126//console].
> Users of QuotaRetriever should pass an existing connection
> ----------------------------------------------------------
>
> Key: HBASE-28716
> URL: https://issues.apache.org/jira/browse/HBASE-28716
> Project: HBase
> Issue Type: Bug
> Components: Admin
> Reporter: Charles Connell
> Assignee: Charles Connell
> Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1
>
>
> Every call to {{HBaseAdmin#getQuota()}} opens a new {{Connection}}, and then
> closes it. As far as I can tell, this is pointless, since it could use the
> existing {{Connection}} object held by the {{HBaseAdmin}}. If you have a
> custom RpcClient (like we do at Hubspot), new connections have an expense
> that we'd rather not pay unnecessarily. I'll submit a PR that addresses this
> situation and similar ones.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
