[
https://issues.apache.org/jira/browse/OOZIE-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426334#comment-13426334
]
Alejandro Abdelnur commented on OOZIE-929:
------------------------------------------
job type should be part of the payload as well. Topics are expensive to create
in a JMS system. Also, who creates a topic, Oozie or the receivers; I assume
Oozie, when a receiver know the topic exists in order to be subscribe. It seems
more adequate to have an OOZIE topic and let subscribers attach with a filter.
I would also presume subscribers will be interested in several jobs, not just
one, thus the jobid as topic does not make sense; more likely the job name
should be part of the message payload as well so a filter can be applied to it.
In addition, JMS should an option disabled by default as it would require a JMS
client bundle with Oozie as well as the JMS configuration. Doing a topic lookup
and creating a JMS connection on every notification is too expensive. IMO this
looks like a candidate for a service that does the JMS setup and manages the
lifecycle of the JMS connection.
Before providing another patch it would be great to have a high level design.
Why not use a pull mechanism like we have for SLAs?
> JMS in NotificationXCommand
> ---------------------------
>
> Key: OOZIE-929
> URL: https://issues.apache.org/jira/browse/OOZIE-929
> Project: Oozie
> Issue Type: New Feature
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Attachments: OOZIE-929.patch
>
>
> Currently for each notification, oozie uses an http connection to send a
> notification. Oozie could use a pub-sub model and a JMS message bus.
> 1. There are a few options for the topic. It could be user generated,
> although this would allow a lot of topics and inconsistent naming. It could
> be per job so users could subscribe to see the notifications of certain jobs.
> It could be done per user.
> 2. Ways to handle the large number of notifications since one notification
> could go to many subscribers. The payload of the notifications should be
> considered. Should it include everything about the action or should it only
> include important things like action id, action status, and time?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
