You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Pragya Mittal (JIRA)" <ji...@apache.org> on 2015/11/03 09:41:27 UTC
[jira] [Commented] (FALCON-1582) Documentation for globally
disabling retries
[ https://issues.apache.org/jira/browse/FALCON-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986921#comment-14986921 ]
Pragya Mittal commented on FALCON-1582:
---------------------------------------
+1, LGTM.
> Documentation for globally disabling retries
> --------------------------------------------
>
> Key: FALCON-1582
> URL: https://issues.apache.org/jira/browse/FALCON-1582
> Project: Falcon
> Issue Type: Improvement
> Components: docs
> Affects Versions: 0.8
> Environment: QA
> Reporter: Pragya Mittal
> Assignee: Pallavi Rao
> Fix For: trunk, 0.8
>
> Attachments: FALCON-1582.patch
>
>
> As part of FALCON-1564 and FALCON-1231, JMS notifications can now be configured on oozie-end instead of listening to system post-processing JMS notification.
> It will also help in attaining globally disabling falcon retries by following these steps :
> * In Falcon runtime.properties, set *.falcon.jms.notification.enabled to false. This will turn off JMS notification in post-processing.
> * Do not copy notification related properties in oozie/conf/oozie-site.xml to oozie-site.xml of the Oozie installation. This will disable Oozie's JMS notification feature
> Once this is done , retry won't happen even if workflow gets killed. I have tested this scenario on my end. I propose to add the documentation for the same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)