falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-69) exception from ConfigurationChangeListener should fail the API
Date Wed, 18 Sep 2013 10:06:53 GMT

    [ https://issues.apache.org/jira/browse/FALCON-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770629#comment-13770629
] 

Shwetha G S commented on FALCON-69:
-----------------------------------

{quote}
What is the behavior of the system if config-store persist is successful, listeners throw
exception and the config store operation is aborted? What happens to the zombie entry in config
store ?
{quote}
Changed the order of steps in store.publish(), remove() and update() so that roll forward
can handle it

{quote}
What happens on system startup ? If one of the clusters is down at startup, will the falcon
server refuse to come up ?
{quote}
changed code to handle this


                
> exception from ConfigurationChangeListener should fail the API
> --------------------------------------------------------------
>
>                 Key: FALCON-69
>                 URL: https://issues.apache.org/jira/browse/FALCON-69
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Shwetha G S
>            Assignee: Shwetha G S
>             Fix For: 0.4
>
>         Attachments: FALCON-69.patch, FALCON-69-v2.patch, FALCON-69-v3.patch
>
>
> Cluster submit succeeds even though copy jars to cluster fails. This creates inconsistent
state. We should fail the API in this case

--
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

Mime
View raw message