[
https://issues.apache.org/jira/browse/HBASE-21710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743016#comment-16743016
]
Duo Zhang commented on HBASE-21710:
-----------------------------------
[~stack] Sir, the goal here is to remove the ClusterConnection.getAdmin
references outside the client library. For these four methods, the problem is
that, we will get a connection, and then cast it to ClusterConnection, and then
use the getAdmin method to connect to the region server.
In my plan, ClusterConnection will be moved to hbase-server module, and will be
backed by an AsyncClusterConnection, and Connection will stay in hbase-client
module, and will be backed by an AsyncConnection, so the Connection instance
which is gotten from the ConnectionFactory.createConnection can not be cast to
ClusterConnection any more...
And in general, the setQuota related methods are included in the Admin
interface, so I think it is also fine to expose these read only information
about the quota usages to user? Especially that, we have already exposed these
things in shell, you can see the 'list_quota_snapshots' and
'list_quota_table_sizes'.
Thanks.
> Add quota related methods to the Admin interface
> ------------------------------------------------
>
> Key: HBASE-21710
> URL: https://issues.apache.org/jira/browse/HBASE-21710
> Project: HBase
> Issue Type: Task
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-21710-v1.patch, HBASE-21710-v1.patch,
> HBASE-21710.patch
>
>
> So we can limit the ClusterConnection usage inside the sync client
> implementation. Now we will use ClusterConnection in QuotaTableUtil, which
> will be a pain when we want to replace the implement of the old sync client
> with the new async client.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
