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:04:00 UTC
[jira] [Commented] (HBASE-25801) Move NamedQueuePayload to
hbase-common
[ https://issues.apache.org/jira/browse/HBASE-25801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327144#comment-17327144 ]
Viraj Jasani commented on HBASE-25801:
--------------------------------------
My point is it will be difficult to let MasterRpcServices or RsRpcServices to again fetch queue records from hbase-client module if we move this class to hbase-client.
> Move NamedQueuePayload to hbase-common
> --------------------------------------
>
> 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.
> ====== Update ======
> A we depend on disruptor for NamedQueueRecord, I do not think it is a good idea to introduce this dependency to our client library. So let's just move the minimum classes to hbase-client or hbase-common instead of the whole namedqueues implementation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)