[jira] [Updated] (HELIX-254) Helix controller should disable participants with mismatched session-id

["Jeff Solanas (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HELIX-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Solanas updated HELIX-254:
-------------------------------

    Sprint: Sprint #4 10/2 - 10/16

> Helix controller should disable participants with mismatched session-id
> -----------------------------------------------------------------------
>
>                 Key: HELIX-254
>                 URL: https://issues.apache.org/jira/browse/HELIX-254
>             Project: Apache Helix
>          Issue Type: Bug
>            Reporter: Zhen Zhang
>            Assignee: Zhen Zhang
>
> Participants may have a mismatched session-id in live-instance (session-id filed in live-instance znode is different from the ephemeral owner id in live-instance znode's meta data) due to race conditions in zk session expiry (e.g. two consecutive long gc). this causes problems when controller sending transition messages to participant and participant just removes the messages due to mismatched session-id. this will lead to infinite loop and flooding zk server.
> While we have a ticket for fixing the mismatched session-id issue, it will be also safe to have a check on helix controller for liveinstance changes. if a liveinstance with mismatched session-id is detected, helix controller should disable the participant.



--
This message was sent by Atlassian JIRA
(v6.1#6144)