dafu created HELIX-123:
--------------------------
Summary: ZkHelixManager.isLeader() should check session id in
addition to instance name
Key: HELIX-123
URL: https://issues.apache.org/jira/browse/HELIX-123
Project: Apache Helix
Issue Type: Bug
Reporter: dafu
Assignee: dafu
Current ZkHelixManager.isLeader() is not checking session id. This is
problematic. In case of session expiry, we might have multiple Helix manager
instances with the same instance name but different session id's. And since
they have the same instance name, if we have a manager leaking, multiple
controllers will take the controller-ship and send multiple state transition
messages.
In distributed-mode, the CONTROLLER_PARTICIPANT will create the leader node and
create a CONTROLLER manager instance. In this case, the leader node contains
the session id of the CONTROLLER_PARTICIPANT not the CONTROLLER, so when
checking against the leader session id, we need to take care of this case as
well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
