falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pragya Mittal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1582) Documentation for globally disabling retries
Date Tue, 03 Nov 2015 09:03:27 GMT

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

Pragya Mittal commented on FALCON-1582:

Then oozie JMS notification will take priority.

> 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

View raw message