[
https://issues.apache.org/jira/browse/FALCON-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700712#comment-14700712
]
Pallavi Rao commented on FALCON-1231:
-------------------------------------
1. Start, suspend, success and failure (killed is also classified as failure)
generates a notification. See
http://oozie.apache.org/docs/4.0.0/DG_JMSNotifications.html for details.
2. Yes. The code checks if the workflow name matches the name pattern of Falcon
workflow name, before processing the message. If it does not, that message is
ignored.
> Improve JobCompletionNotification Service
> -----------------------------------------
>
> Key: FALCON-1231
> URL: https://issues.apache.org/jira/browse/FALCON-1231
> Project: Falcon
> Issue Type: Sub-task
> Reporter: Pallavi Rao
> Assignee: Pallavi Rao
> Attachments: FALCON-1231.patch, OozieJobStatusNotification.pdf
>
>
> Workflow completion is currently dependent on post processing action putting
> messages (success/failure) to a JMS queue.
> When failures occur on Hadoop / Oozie, the post processing action may not
> get executed either. In such cases, Falcon will be blind to the status of the
> workflow and re-tries will not happen.
> Explore url notification of oozie to get job completion notifications. Fall
> back on polling when workflows run beyond SLA.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
