[
https://issues.apache.org/jira/browse/HBASE-25183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214295#comment-17214295
]
Michael Stack commented on HBASE-25183:
---------------------------------------
I've been looking at this because of "HBASE-25185 Remove the usage of
MetaTableAccessor in hbase-balancer" which I was looking at because of
"HBASE-24609 Move MetaTableAccessor out of hbase-client"
The current module dependency has it that balancer depends on client but not on
server. How are we to have a smart balancer that only has client access but no
access to info only the Master knows? This seems incorrect to me.
Looking at "HBASE-23933 Separate a hbase-balancer or hbase-assignment module"
where we make the hbase-balancer module, there is some movement of balancer
classes out to the new hbase-balancer module -- some base classes are moved but
not the default Stochastic balancer implementation.. it is too intertwined w/
master internals. Bits of the Favored Nodes implementation are moved but not
all (meanwhile we've manufactured what now seems like an artificial scenario,
HBASE-25185).
Is the motiviation here just shrinking hbase-server module or is there some
other driver?
> Move more balancer related classes to hbase-balancer
> ----------------------------------------------------
>
> Key: HBASE-25183
> URL: https://issues.apache.org/jira/browse/HBASE-25183
> Project: HBase
> Issue Type: Umbrella
> Components: Balancer
> Reporter: Duo Zhang
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
