You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Craig Peters (Created) (JIRA)" <ji...@apache.org> on 2011/11/04 19:07:51 UTC

[jira] [Created] (OOZIE-599) Enable Oozie to be a subscriber to a topic on a message bus topic for job end notifications

Enable Oozie to be a subscriber to a topic on a message bus topic for job end notifications
-------------------------------------------------------------------------------------------

                 Key: OOZIE-599
                 URL: https://issues.apache.org/jira/browse/OOZIE-599
             Project: Oozie
          Issue Type: New Feature
            Reporter: Craig Peters


Oozie should be able to listen to a user configurable topic on a message bus via JMS for job completion notifications.  This requires use a general inter-component communication system using the publish/subscribe model provided by ActiveMQ.  http://activemq.apache.org/  The value for Oozie and Hadoop is to enable a less brittle communication because Oozie would not poll the Job Tracker for job completion in the absence of a URL or a timeout.

Hadoop currently implements a call back URL to notify clients including Oozie that a job has completed.  See https://issues.apache.org/jira/browse/MAPREDUCE-3028.  This implementation has a number of challenges including that only one client can get notification easily and the implementation blocks the thread so that a bad URL blocks job tracker execution.  This requires Map Reduce to enable a way for a job creator to specify which topic to which to publish the job end notification message.

--
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

        

[jira] [Commented] (OOZIE-599) Enable Oozie to be a subscriber to a topic on a message bus topic for job end notifications

Posted by "Craig Peters (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144233#comment-13144233 ] 

Craig Peters commented on OOZIE-599:
------------------------------------

For more on the blocking issue on the job tracker call back in Hadoop 0.23 see https://issues.apache.org/jira/browse/OOZIE-597
                
> Enable Oozie to be a subscriber to a topic on a message bus topic for job end notifications
> -------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-599
>                 URL: https://issues.apache.org/jira/browse/OOZIE-599
>             Project: Oozie
>          Issue Type: New Feature
>            Reporter: Craig Peters
>
> Oozie should be able to listen to a user configurable topic on a message bus via JMS for job completion notifications.  This requires use a general inter-component communication system using the publish/subscribe model provided by ActiveMQ.  http://activemq.apache.org/  The value for Oozie and Hadoop is to enable a less brittle communication because Oozie would not poll the Job Tracker for job completion in the absence of a URL or a timeout.
> Hadoop currently implements a call back URL to notify clients including Oozie that a job has completed.  See https://issues.apache.org/jira/browse/MAPREDUCE-3028.  This implementation has a number of challenges including that only one client can get notification easily and the implementation blocks the thread so that a bad URL blocks job tracker execution.  This requires Map Reduce to enable a way for a job creator to specify which topic to which to publish the job end notification message.

--
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