falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peeyush Bishnoi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1405) Oozie workflow should not fail if post-processing fails
Date Fri, 04 Sep 2015 08:53:46 GMT

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

Peeyush Bishnoi commented on FALCON-1405:
-----------------------------------------

[~nperiwal] Yes I agree with you that failure reason might be available in regular service
component logs. But I have a opinion that if reason is logged in falcon.application.log due
to which post-processing fails it will be highly useful to the users. This will help specially
to the user's who don't know much about Hadoop. Later, for narrow down the issue, respective
component regular logs can be checked for further detailed exception for the issue.

> Oozie workflow should not fail if post-processing fails
> -------------------------------------------------------
>
>                 Key: FALCON-1405
>                 URL: https://issues.apache.org/jira/browse/FALCON-1405
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Pallavi Rao
>            Assignee: Narayan Periwal
>         Attachments: FALCON-1405-v0.patch, FALCON-1405-v1.patch
>
>
> Currently, even if the user workflow succeeds and post-processing fails, the workflow
is marked as failed.
> IMO, the post-processing should be an optional step. We should wire workflow to succeed
even if the post-processing fails. Especially, after FALCON-1231, we won't even depend on
post-processing for completion notification.



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

Mime
View raw message