[
https://issues.apache.org/jira/browse/FALCON-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649294#comment-14649294
]
Peeyush Bishnoi commented on FALCON-1231:
-----------------------------------------
[~pallavi.rao] After going through the details for the Oozie callback action,
it looks like that this will send the post workflow details of Falcon instance
to JMS directly. Currently, in Falcon we are sending the post workflow details
of Falcon instance to JMS through FalconPostProcessing class.
So if we agree to create notification listener (approach 2 from FALCON-1313)
for generating email notification, then we need to read the post workflow
details received from JMS server of Oozie callback action.
> 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: 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)
