[
https://issues.apache.org/jira/browse/FALCON-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700709#comment-14700709
]
Pallavi Rao commented on FALCON-1231:
-------------------------------------
JMS notification in Post processing of Falcon would not help in cases where the
workflow got killed or failed in the post-processing, there will not be any
failure notification. Also, there won't any notifications when workflow starts
or gets suspended. Using Oozie's JMS notification addresses these problems.
Since Oozie JMS notification is not an action, the notification will be
generated for every status change of the workflow.
If Oozie JMS notification is enabled, the notifications from post-processing
will be ignored, as there will be a notification from Oozie. With this patch,
any new workflows should not generated system JMS notifications in
post-processing. Just noticed that I had missed checking in that change as part
of the patch. Will update the patch.
> 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)
