[
https://issues.apache.org/jira/browse/HELIX-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kanak Biscuitwala updated HELIX-448:
------------------------------------
Fix Version/s: 0.6.4
0.7.1
> Call onCallback for CustomCodeCallbackHandler for FINALIZE type
> ---------------------------------------------------------------
>
> Key: HELIX-448
> URL: https://issues.apache.org/jira/browse/HELIX-448
> Project: Apache Helix
> Issue Type: Bug
> Reporter: Kanak Biscuitwala
> Assignee: Kanak Biscuitwala
> Fix For: 0.7.1, 0.6.4
>
>
> Many use cases assume that onCallback will be invoked with type FINALIZE when
> leadership is lost so that there is an opportunity to clean up. However, this
> is not the case, and the previous leader has no idea that it's not leader
> anymore.
> Long term the right thing to do is to split onCallback into 3 different
> methods, but for now, we should also invoke onCallback with the appropriate
> type, since this seems to be the expected behavior.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
