You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2021/04/22 07:00:12 UTC

[jira] [Commented] (HBASE-25801) Move NamedQueuePayload to hbase-client

    [ https://issues.apache.org/jira/browse/HBASE-25801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327139#comment-17327139 ] 

Viraj Jasani commented on HBASE-25801:
--------------------------------------

NamedQueueRecorder is the primary interface to fetch records from specific queues. Hence, NamedQueueRecorder is kept at both places HMaster and RegionServer, so that both Master and RS RpcServices can use it to retrieve records from given queue. I am not sure if moving to client will benefit much.

If it is about balancer adding records to Queue interface, I think it is still possible if hbase-balancer has dependency on hbase-server right?

> Move NamedQueuePayload to hbase-client
> --------------------------------------
>
>                 Key: HBASE-25801
>                 URL: https://issues.apache.org/jira/browse/HBASE-25801
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Operability
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>
> We use this class to record the balancer decision in LoadBalancer, so if we want to move LoadBalancer to hbae-balancer, we also need to move NamedQueueRecord related classes out of hbase-server. Since we use a system table to record, hbase-client will be a suitable place.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)