[
https://issues.apache.org/jira/browse/FALCON-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867654#comment-13867654
]
Shaik Idris Ali commented on FALCON-38:
---------------------------------------
1. There are about 40 constants in the file and few action names existed
already, so didn't bother to extract.
2. For retention once we add Falcon post-processing it will be taken care,
currently message is sent on to user topic.
> 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,
> Fix For: 0.4
>
> Attachments: FALCON-38.patch
>
> 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)
