falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkat Ramachandran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1602) Recoverability of Falcon Processes when ActiveMQ down for sometime
Date Sun, 31 Jan 2016 22:49:39 GMT

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

Venkat Ramachandran commented on FALCON-1602:

[~pallavi.rao] Would it make sense to have a watcher on the activemq? If activemq goes down,
that should be notified so that the service can be fixed. Polling oozie until then could be
an option to catch up the task completions.

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

View raw message