[
https://issues.apache.org/jira/browse/FALCON-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712631#comment-14712631
]
Pallavi Rao commented on FALCON-1231:
-------------------------------------
[~yzheng-hortonworks], I double checked the Oozie JMS notification to see if it
distinguishes between FAILED and KILLED. The JMS message header classifies both
as failure, but, the JSON message has the actual status (KILLED or FAILED).
Since, my patch uses the status in the message and not the header, the uploaded
patch will satisfy your requirement too. WorkflowExecutionContext.getStatus()
will give you the correct status.
> 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, 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)
