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-1231) Improve JobCompletionNotification Service
Date Fri, 21 Aug 2015 08:08:46 GMT

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

Pallavi Rao commented on FALCON-1231:
-------------------------------------

WorkflowExecutionContext is constructed using the Job configuration of Oozie. When we receive
a JMS notification Oozie, the code queries Oozie back with the workflow id and retrieves the
configuration. Once the configuration is obtained, the context can be constructed. See the
patch for more details, especially, WorkflowJobEndNotificationService.updateContextFromWFConf.

That way, none of the downstream listeners are affected. They continue to work on WorkflowExecutionContext.

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

Mime
View raw message