[jira] [Comment Edited] (FALCON-644) Falcon message producer masks errors in Post processing

["Venkatesh Seetharam (JIRA)" <ji...@apache.org>]

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

Venkatesh Seetharam edited comment on FALCON-644 at 9/3/14 6:14 PM:
--------------------------------------------------------------------

On second thoughts, I think this can be handled gracefully with my proposal in FALCON-327, specifically FALCON-490. I had proposed to serialize the message to HDFS (FALCON-486) and then send the message as it is today. Have a thread in Falcon to poll HDFS for these serialized messages and notify for missed messages. Need to think about filtering already handled messages - may be look up graph db to see if an entry exists?

This should solve the holes issue and keep the code simple as well.

Thoughts? 

In any case, created FALCON-665 for handling message failures and FALCON-666 for alerts.


was (Author: svenkat):
On second thoughts, I think this can be handled gracefully with my proposal in FALCON-327, specifically FALCON-490. I had proposed to serialize the message to HDFS (FALCON-486) and then send the message as ii is today. Have a thread in Falcon to poll HDFS for these serialized messages and notify for missed messages. Need to think about filtering already handled messages - may be look up graph db to see if an entry exists?

This should solve the holes issue and keep the code simple as well.

Thoughts? 

In any case, created FALCON-665 for handling message failures and FALCON-666 for alerts.

> Falcon message producer masks errors in Post processing
> -------------------------------------------------------
>
>                 Key: FALCON-644
>                 URL: https://issues.apache.org/jira/browse/FALCON-644
>             Project: Falcon
>          Issue Type: Bug
>          Components: messaging
>    Affects Versions: 0.6
>            Reporter: Sowmya Ramesh
>            Assignee: Venkatesh Seetharam
>            Priority: Blocker
>             Fix For: 0.6
>
>         Attachments: FALCON-644-v1.patch, FALCON-644.patch
>
>
> In JMSMessageProducer all the exceptions are caught and success is returned [return 0] by default. Oozie will indicate that this WF action was successful as Falcon Messaging returns success.
> WF shouldn't be failed if post-processing fails but instead of masking errors this can be controlled in the WF decision on failure.
> {noformat}
> <action name='succeeded-post-processing'>
> ...
>  <ok to="end"/>
> <!-- Shouldn't fail the WF if post processing fails -->
>  <error to="end"/>
>  </action>
> {noformat}
> Thoughts?



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