[
https://issues.apache.org/jira/browse/BOOKKEEPER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436740#comment-13436740
]
Sijie Guo commented on BOOKKEEPER-363:
--------------------------------------
{quote}
1) Hedwig hubs only update the load while claiming topics. We should also
update the load while releasing topics.
{quote}
ah, ur right. it would make the requests really unbalance if some hubs release
topics periodically.
{quote}
we introduce a rebalanceCluster() function in the HubServerManager interface.
{quote}
I am guessing who does the balance work. Each hub server runs independently? Or
a hub server would be elected as a leader to do it?
I am doubting if each hub server runs independently, hub servers might make a
wrong decision to releasing topics, which cause lots of topics to be released.
> Re-distributing topics among newly added hubs.
> ----------------------------------------------
>
> Key: BOOKKEEPER-363
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-363
> Project: Bookkeeper
> Issue Type: Bug
> Components: hedwig-server
> Reporter: Aniruddha
>
> When a new hub is added to an already existing hedwig cluster, that hub
> should pick up some of the topics. Currently the mechanism hedwig provides is
> to configure the time for which a topic is retained. A better approach might
> be to run a re-balancer thread that periodically checks if topics are
> distributed evenly among hubs and if not, releases some topics to balance the
> load.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
