[
https://issues.apache.org/jira/browse/BOOKKEEPER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aniruddha updated BOOKKEEPER-363:
---------------------------------
Description:
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.
https://reviews.apache.org/r/6700/
There is a race condition while updating load as mentioned in the comments and
that is not handled in this review.
was: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.
> 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
> Assignee: Aniruddha
> Attachments: BK-363.patch
>
>
> 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.
> https://reviews.apache.org/r/6700/
> There is a race condition while updating load as mentioned in the comments
> and that is not handled in this review.
--
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
