falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shaik Idris Ali (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-38) Falcon's parent workflow actions (pre-processing & post-processing) should have mulitple retries
Date Thu, 09 Jan 2014 23:21:52 GMT

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

Shaik Idris Ali commented on FALCON-38:
---------------------------------------

1. Added configurable oozie retries and interval for Falcon actions like recordsize, succeeded-postprocessing
and failed-postprocessing

2. Updated Oozie workflow XSD with latest 3.0 definition.


> Falcon's parent workflow actions (pre-processing & post-processing) should have mulitple
retries
> ------------------------------------------------------------------------------------------------
>
>                 Key: FALCON-38
>                 URL: https://issues.apache.org/jira/browse/FALCON-38
>             Project: Falcon
>          Issue Type: Bug
>          Components: oozie, process
>    Affects Versions: 0.3
>         Environment: Oozie 3.2.X +, Falcon 0.1
>            Reporter: Shaik Idris Ali
>            Assignee: Shaik Idris Ali
>              Labels: failures, jms, oozie, retries,
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Oozie actions may fail for various transient and non-transient problems arising in Hadoop,
Network etc.
> Falcon handles user-workflow action failures by sending a JMS notification to ActiveMQ
(post-processing action in parent-wf), this message is used to provide automatic retries based
on various retry policies defined in Process.xml. However, post-processing action of Falcon
itself might fail and workflow may remain in killed/suspended state.
> Oozie provides OOTB retires that can be configured per action, we should leverage this
to provide Falcon's parent workflow action reruns.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message