You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@helix.apache.org by GitBox <gi...@apache.org> on 2019/09/13 21:22:30 UTC
[GitHub] [helix] jiajunwang commented on issue #466: Integrate the WAGED
rebalancer with all the related components.
jiajunwang commented on issue #466: Integrate the WAGED rebalancer with all the related components.
URL: https://github.com/apache/helix/pull/466#issuecomment-531395357
> If the constraint factory/wagedRebalancer fails to produce the mapping, should we put the cluster in maintenance mode or treat it as a NOP? I'd like to guide us to think about in what scenarios putting the cluster under maintenance would be appropriate.
The current design returns the previous mapping if a calculation fails (this is not done yet). Entering maintenance mode means we need to auto exist as well. This makes maintenance mode management more complicated. So I would prefer keeping it simple for now.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@helix.apache.org
For additional commands, e-mail: reviews-help@helix.apache.org