You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "sandeep samudrala (JIRA)" <ji...@apache.org> on 2015/11/02 15:52:27 UTC

[jira] [Commented] (FALCON-1571) Falcon retry is happening infinitely in case of sub workflow getting killed.

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

sandeep samudrala commented on FALCON-1571:
-------------------------------------------

I have moved it out of 0.8 as its not an issue occurred in 0.8 and exists since long. The workaround would be to move to coordinator action rerun rather than workflow rerun in falcon.

I am attaching the logs of the specific case where oozie has thrown null pointer exception and falcon keeps retrying on catching the exception in RetryConsumer.


> Falcon retry is happening infinitely in case of sub workflow getting killed.
> ----------------------------------------------------------------------------
>
>                 Key: FALCON-1571
>                 URL: https://issues.apache.org/jira/browse/FALCON-1571
>             Project: Falcon
>          Issue Type: Bug
>          Components: common
>            Reporter: sandeep samudrala
>            Assignee: sandeep samudrala
>
> The issue is happening only in specific cases, which is a curious case of the coord action being rerun both from falcon(workflow rerun) and also oozie rerun(coord action rerun), in which case when falcon tries to rerun the older workflow, by then the external Id of the coordinator action is updated to a new workflow because of a oozie rerun.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)