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

Ying Zheng commented on FALCON-1231:
------------------------------------

[~pallavi.rao] A couple of questions: 

1. Would you be able to capture all the status change including suspended and 
killed? I'm asking because instance search would need all the up-to-date 
status. If so, we plan to use your notification code instead of writing another 
one separately.

2. Can oozie JMS distinguish jobs between Falcon and others, so falcon only 
gets JMS notifications of jobs created by Falcon?

Thanks!

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

Reply via email to