You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@helix.apache.org by "Kanak Biscuitwala (JIRA)" <ji...@apache.org> on 2014/05/29 00:22:02 UTC

[jira] [Created] (HELIX-448) Call onCallback for CustomCodeCallbackHandler for FINALIZE type

Kanak Biscuitwala created HELIX-448:
---------------------------------------

             Summary: 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


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)