falcon-dev mailing list archives

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

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

Srikanth Sundarrajan commented on FALCON-1405:

+1. This can be committed.

While on this, [~sandeep.samudrala], was suggesting in an offline conversation that the post
processing be moved to the falcon server. Which is indeed the way forward with the new scheduler
work happening. I am inclined as it seems to lower the resource utilization, while burdening
the falcon server a bit more. What do others feel ? Flip side of course is that the logs haven't
been moved (as there might be a delay in when falcon server picks this up), and users wonder
why logs aren't available even after the workflow has completed.

> 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

View raw message