You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@helix.apache.org by GitBox <gi...@apache.org> on 2019/07/18 18:04:15 UTC
[GitHub] [helix] i3wangyi commented on issue #343: Fine-grained state
transition throttling and respect MIN_ACTIVE replica
i3wangyi commented on issue #343: Fine-grained state transition throttling and respect MIN_ACTIVE replica
URL: https://github.com/apache/helix/issues/343#issuecomment-512924648
I feel like we need to put more background knowledge and context on the topic. For example, why Helix will treat the previous ongoing offline -> slave as recovery balance given it was kicked off as load balance. One naive question, I understand the current limitation is **helix controller doesn't know the historical context about any ongoing state transitions in a participant** (is it true). Is it because of the **state transition message for the participant** get consumed? What if we preserve the pending message until completion and controller would be able to know the historical context? pros and cons?
Let's put more background and context of the problem to have a meaningful discussion.
----------------------------------------------------------------
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