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-1564) Defined retry attempts are not happening for Falcon instance
Date Thu, 29 Oct 2015 04:47:27 GMT

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

Pallavi Rao commented on FALCON-1564:

The notifications produced by older processes will continue to be processed. That way it is
backward compatible. Once Oozie JMS notification is enabled, all listener services depending
on the JMS notification will continue to work as before. That contract has been preserved.

The idea is to eventually move away from post-processing all together as it consumes an additional
resource on the grid and increases overall execution time of the workflow. Towards that end,
the new processes will not produce notification and will depend on Oozie notification. Consuming
Oozie notification and also producing our own notification is just duplicate and redundant.

> Defined retry attempts are not happening for Falcon instance
> ------------------------------------------------------------
>                 Key: FALCON-1564
>                 URL: https://issues.apache.org/jira/browse/FALCON-1564
>             Project: Falcon
>          Issue Type: Bug
>          Components: rerun
>            Reporter: Peeyush Bishnoi
>            Assignee: Pallavi Rao
>            Priority: Blocker
>             Fix For: trunk
> On running the Falcon process entity with retry option and with defined number of attempts,
I have found that not a single retry is happening upon instance failure.

This message was sent by Atlassian JIRA

View raw message