falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1231) Improve JobCompletionNotification Service
Date Sat, 01 Aug 2015 08:50:04 GMT

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

Ajay Yadava commented on FALCON-1231:
-------------------------------------

[~yzheng-hortonworks]

JMS notifications are slightly better approach in my opinion. They are more resilient than
HTTP notification, even though there are retries for HTTP notifications.  They are also slightly
cleaner approach when we want multiple consumers for the same notifications.  My 2 cents.

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

Mime
View raw message