falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandeep samudrala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1926) Filter out effectively non-falcon related JMS messages from Oozie
Date Mon, 25 Apr 2016 16:48:12 GMT

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

sandeep samudrala commented on FALCON-1926:
-------------------------------------------

I don't see any issue in dropping post-processing from falcon actions. The same messages we
are getting from oozie wf notifications and which is working well too.
Retry/latererun are also dependent on these notifications, but they too are working fine with
oozie notifications.
Ideally we can remove post-processing, which means we save 1 container for each triggered
instance.


> Filter out effectively non-falcon related JMS messages from Oozie
> -----------------------------------------------------------------
>
>                 Key: FALCON-1926
>                 URL: https://issues.apache.org/jira/browse/FALCON-1926
>             Project: Falcon
>          Issue Type: Improvement
>          Components: messaging
>    Affects Versions: trunk
>            Reporter: Venkatesan Ramachandran
>            Assignee: Venkatesan Ramachandran
>
> Enabling Oozie JMS will flood the falcon JMS topic with both falcon and non-falcon submitted
workflow status notifications, where as Falcon is only interested in the messages for the
workflows it submitted. 
> Using JMS selector, only relevant messages need to be retrieved and processed further.



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

Mime
View raw message