[
https://issues.apache.org/jira/browse/FALCON-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636447#comment-14636447
]
Ajay Yadava commented on FALCON-1313:
-------------------------------------
{quote}
We cannot ask users to add email action to their workflows because not all
workflows are created by users (Feed replication jobs).
{quote}
That's a very good point but what is the use of success notification in this
case? Processes will automatically start as soon as feed is available.
Let's say the job failed first time, you will get an email, by the time you go
and check, falcon will automatically retry it. What's the use of email now?
Another point to consider: What will be the most common cause of such failures?
Infrastructure issues. In such cases, not one feed
will fail but lots of feeds will fail and on every retry you will get an email.
Now it will become unmanageable. Same users will now complain of noise.
Let's say you solve for the above cases, what will happen when replication is
stuck or too slow. The user should have been alerted but he is not.
Also, reliance on email infrastructure is not the best option.
The user might have put it that they want success/failure but the actual use
case is that some data which should have been available is not available and
SLA monitoring should solve it.
> 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)
