helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dafu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HELIX-43) Add support for error->dropped transition
Date Mon, 25 Mar 2013 21:11:18 GMT

    [ https://issues.apache.org/jira/browse/HELIX-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613132#comment-13613132

dafu commented on HELIX-43:

1) DROPPED logic will remain the same. We will first transit to user defined initial state
and then to DROPPED state. 

2) StateModel.onError() should provide the state-transition message that causes the error.
It should look like StateModel.onError(Message message, NotificationContext context).We could
either embed error context into notification context or provide an addition error context
as an argument. We probably need to provide context for drop() and reset() also

3) if onError() fails, we can still transit to ERROR or we can go directly to FATAL. if drop/reset()
fails, we remain in FATAL.
> Add support for error->dropped transition
> -----------------------------------------
>                 Key: HELIX-43
>                 URL: https://issues.apache.org/jira/browse/HELIX-43
>             Project: Apache Helix
>          Issue Type: New Feature
>    Affects Versions: 0.6.0-incubating
>            Reporter: dafu
>            Assignee: dafu
> currently helix doesn't support any auto transition from error state. but in some situations
it might required to drop a partition in error state.

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