helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kishore gopalakrishna (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HELIX-30) ZkHelixManager.carryOverPreviousCurrentState() should use a special merge logic
Date Tue, 29 Jan 2013 23:03:13 GMT

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

kishore gopalakrishna updated HELIX-30:

    Fix Version/s: 0.6.1-incubating
> ZkHelixManager.carryOverPreviousCurrentState() should use a special merge logic
> -------------------------------------------------------------------------------
>                 Key: HELIX-30
>                 URL: https://issues.apache.org/jira/browse/HELIX-30
>             Project: Apache Helix
>          Issue Type: Bug
>            Reporter: Shi Lu
>            Assignee: dafu
>             Fix For: 0.6.1-incubating
> We have a potential race condition for ZkHelixManager.carryOverPreviousCurrentState().
> It happens after addLiveInstance(), so it is possible that the participant has received
some message from controller, updated current state then the currentstate is overwritten by
the carry over.
> when we carryover, we should provide a merge logic such that only partition keys that
does not exist on the existing current state are updated. This will solve the race condition

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

View raw message