[
https://issues.apache.org/jira/browse/HELIX-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kanak Biscuitwala reassigned HELIX-281:
---------------------------------------
Assignee: Kanak Biscuitwala (was: Zhen Zhang)
> Need to optimize the scenario that multiple Message change can stop external
> view update
> -----------------------------------------------------------------------------------------
>
> Key: HELIX-281
> URL: https://issues.apache.org/jira/browse/HELIX-281
> Project: Apache Helix
> Issue Type: Bug
> Reporter: Shi Lu
> Assignee: Kanak Biscuitwala
> Priority: Critical
>
> We have seen the following behavior in the relay cluster startup:
> controller is full time doing onMessage() callback, although all the current
> state has already been updated. As all state transitions are done, all the
> Message update callback in controller side becomes NO-OP but stops the
> current state from being updated. As there are so many onMessage change
> callbacks, ExternalView does not get updated in hours. This is going to be a
> blocking perf issue in big clusters.
> One work-around is to switch the controller if the current controller is in
> this Message update loop.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
