You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@falcon.apache.org by "Ajay Yadava (JIRA)" <ji...@apache.org> on 2015/07/25 13:42:04 UTC

[jira] [Commented] (FALCON-1329) Falcon idempotent behaviour breaks in some cases

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

Ajay Yadava commented on FALCON-1329:
-------------------------------------

I will try to add detailed steps to reproduce later. However, one common theme was if one falcon server threw an unhandled exception then it won't get submitted in prism. If it doesn't get submitted in prism then it won't get deleted. Users used to get stuck as they won't be able to update and resubmit the entity or delete it from some servers where they were successful. 

> Falcon idempotent behaviour breaks in some cases
> ------------------------------------------------
>
>                 Key: FALCON-1329
>                 URL: https://issues.apache.org/jira/browse/FALCON-1329
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Ajay Yadava
>            Assignee: Ajay Yadava
>            Priority: Critical
>             Fix For: 0.7
>
>
> In certain cases Idempotent behaviour of falcon is broken. Sometimes, entities go in a zombie state. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)