[
https://issues.apache.org/jira/browse/HBASE-25801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-25801:
------------------------------
Description:
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 instead of the whole namedqueues implementation.
was: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.
> 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.
> ====== 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 instead of the whole namedqueues
> implementation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
