Thanks Shi for this feature. It is quite useful in AUTO_REBALANCE mode. So now one can say a node can host max of P partitions
I have few questions on the impl, what is the better place to enforce this constraint, your changes do that in the idealstate computation stage, is it a better idea to do this in throttling stage?. This will allow us to enforce this constraint at resource, node and cluster level similar to the way we can specify constraints on transitions at multiple levels. This would allow us to use this feature across different modes( AUTO, CUSTOM). Thoughts ? thanks, Kishore G On Tue, Feb 19, 2013 at 4:23 PM, Shi Lu (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/HELIX-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581795#comment-13581795] > > Shi Lu commented on HELIX-49: > ----------------------------- > > > https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=commit;h=1609d5cb3451c0fe24afc49fbae577e80fd6d2be > > > Add support to specify max partition per instance for AUTO-REBALANCE mode > > ------------------------------------------------------------------------- > > > > Key: HELIX-49 > > URL: https://issues.apache.org/jira/browse/HELIX-49 > > Project: Apache Helix > > Issue Type: Bug > > Reporter: Shi Lu > > Assignee: Shi Lu > > > > > -- > 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 >
