You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@helix.apache.org by "Kanak Biscuitwala (JIRA)" <ji...@apache.org> on 2013/08/26 18:30:51 UTC
[jira] [Comment Edited] (HELIX-214) User-defined rebalancer should
never use SEMI_AUTO code paths
[ https://issues.apache.org/jira/browse/HELIX-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750209#comment-13750209 ]
Kanak Biscuitwala edited comment on HELIX-214 at 8/26/13 4:30 PM:
------------------------------------------------------------------
Attached the patch. Previously, even the user-defined rebalancer would use the old ideal state calculator initially and then get invoked for the rebalance stage. This is no longer the case, as the partitions are initialized, but a mapping is not computed until the user-defined rebalancer is first run.
Code review: https://reviews.apache.org/r/13785/
was (Author: kanak):
Attached the patch. Previously, even the user-defined rebalancer would use the old ideal state calculator initially and then get invoked for the rebalance stage. This is no longer the case, as the partitions are initialized, but a mapping is not computed until the user-defined rebalancer is first run.
> User-defined rebalancer should never use SEMI_AUTO code paths
> -------------------------------------------------------------
>
> Key: HELIX-214
> URL: https://issues.apache.org/jira/browse/HELIX-214
> Project: Apache Helix
> Issue Type: Bug
> Reporter: Kanak Biscuitwala
> Assignee: Kanak Biscuitwala
> Attachments: 0001-HELIX-214-User-defined-rebalancer-should-never-use-S.patch
>
>
> The user-defined rebalancer should always return the full mapping, and should be able to do this from the start, and not after an initial balance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira