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

Balu Vellanki commented on FALCON-1313:
---------------------------------------

[~pallavi.rao] and [~ajayyadava]
Regardless of how we do it, I have heard from customers/support-teams first 
hand about the need to get notifications on failure of Falcon jobs. Email is 
preferred form of notification. We cannot ask users to add email action to 
their workflows because not all workflows are created by users (Feed 
replication jobs). 

[~peeyushb] :  I have a comment and a question. 

Comment : I am more in favor is approach 2 where Falcon generates the email 
notification on success/failure of the jobs. This way Falcon will not have to 
worry about configuring SMTP service on Oozie server. It is better to have 
control within  If JMS notifications are not reliable, and if multiple services 
listed by you depend on the notifications, may be we must work on making the 
notifications reliable as well. 

Question : Do we expect admin email-address to be specified in 
runtime.properties? 

Falcon has reliable API to check status of instances. If making JMS 
notifications reliable is not feasible, can we have a Falcon Service that 
periodically checks status of instances for registered falcon entities and 
email the users? But it feels like a clunky solution. 

> Generate notification for Falcon job status
> -------------------------------------------
>
>                 Key: FALCON-1313
>                 URL: https://issues.apache.org/jira/browse/FALCON-1313
>             Project: Falcon
>          Issue Type: New Feature
>          Components: common
>    Affects Versions: 0.6.1
>            Reporter: Peeyush Bishnoi
>            Assignee: Peeyush Bishnoi
>         Attachments: Falconjobstatusnotification.pdf
>
>
> Falcon should generate Email based notification for job status to the 
> user/group when job finish either with success/failure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to