falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pallavi Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1313) Generate notification for Falcon job status
Date Tue, 21 Jul 2015 04:53:04 GMT

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

Pallavi Rao commented on FALCON-1313:

Let me try to articulate my concerns. We can get on a call if required.
Approach 1 : Extend the workflow by leveraging Oozie email action.
1. If the users are expected to configure the SMTP server in Oozie, why not just let them
add an email notification in their user workflow itself? We'll end up taking in the same set
of parameters anyway.

Approach 2 : Create notification listener to capture the job status through JMSMessageConsumer
1. Everything is fine when all sub-workflows and sub-actions succeed. But, when post-processing
fails (user workflow may have succeeded), there will be no JMS notification, hence, Falcon
will not be aware of the status of that workflow. In fact, Falcon suffers from the same problem
in case of retries too. At InMobi, we have seen that retries from Falcon side usually don't
happen because the JMS notification never came due to failure. This is what I meant when I
said, the JMS notifications are not reliable. 

> 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

View raw message