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

Posted to dev@falcon.apache.org by "Pallavi Rao (JIRA)" <ji...@apache.org> on 2016/01/25 07:15:39 UTC

[jira] [Issue Comment Deleted] (FALCON-1602) Recoverability of Falcon Processes when ActiveMQ down for sometime

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

Pallavi Rao updated FALCON-1602:
--------------------------------
    Comment: was deleted

(was: Made some changes in places where the interface contract was violated.

Will checkin this patch.)

> Recoverability of Falcon Processes when ActiveMQ down for sometime 
> -------------------------------------------------------------------
>
>                 Key: FALCON-1602
>                 URL: https://issues.apache.org/jira/browse/FALCON-1602
>             Project: Falcon
>          Issue Type: Task
>            Reporter: pavan kumar kolamuri
>         Attachments: FALCON-1758-v1.patch
>
>
> With Falcon Native Scheduler activemq is used for job completion notifications from oozie. When activemq is down for sometime, and oozie fails to send notifications of completion of workflows of process instances even after retries. Then those instances won't mark as completed in Falcon state store. Then for that processes new instances won't be launched assuming old one's still running. There should be some recoverability in these cases.



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