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-53) Allow partitions to be dropped automatically when their instance dies
Date Tue, 19 Mar 2013 21:15:15 GMT

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

kishore gopalakrishna updated HELIX-53:

    Assignee: Shi Lu
> Allow partitions to be dropped automatically when their instance dies 
> ----------------------------------------------------------------------
>                 Key: HELIX-53
>                 URL: https://issues.apache.org/jira/browse/HELIX-53
>             Project: Apache Helix
>          Issue Type: Improvement
>          Components: helix-core
>    Affects Versions: 0.6.0-incubating, 0.6.1-incubating
>            Reporter: Abhishek Rai
>            Assignee: Shi Lu
>            Priority: Minor
> Currently, when creating a session for a new participant, Helix resets current states
of all assigned partitions from previous session of the same participant to the initial state.
This may be undesirable for deployments where Helix session and assigned partitions by the
participant are tightly coupled. In such a setup, when a participant loses a session, it also
loses all associated partitions.  The current behavior triggers transitions back to the ideal
state which may or may not be desirable.  Possible workarounds:
> (1) update ideal state to DROPPED on noticing that an instance is not live anymore
> (2) (suggested by Kishore) safely clear state from old participant session before creating
a new session.  I'm using this one and so far it's working OK for me.

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