You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2013/08/06 23:04:47 UTC

[jira] [Updated] (OOZIE-615) Support high availability for the Oozie service

     [ https://issues.apache.org/jira/browse/OOZIE-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Kanter updated OOZIE-615:
--------------------------------

    Attachment: OOZIE-615.patch

New patch addresses Alejandro's comments from RB.  Mostly minor refactoring, clarifying things, etc.  Biggest change was to how the logs are collated from other servers; I reworked that logic to not load all of the logs into memory anymore (ZKXLogStreamingService).  
                
> Support high availability for the Oozie service
> -----------------------------------------------
>
>                 Key: OOZIE-615
>                 URL: https://issues.apache.org/jira/browse/OOZIE-615
>             Project: Oozie
>          Issue Type: New Feature
>    Affects Versions: trunk
>            Reporter: Craig Peters
>            Assignee: Robert Kanter
>             Fix For: trunk
>
>         Attachments: OOZIE-615.patch, OOZIE-615.patch, OOZIE-615.patch, OOZIE-615.patch, OOZIE-615.patch, OOZIE-615.patch, OozieHADesign.pdf, Oozie HA Overview.pdf, zookeeper_yahoo_code.zip
>
>
> As Oozie becomes a critical component in the Hadoop ecosystem users needs assured availability of the services provided by Oozie.  To support this need Oozie should include a new feature to support high availability.  This feature needs to take into consideration that Oozie provides RESTful APIs, Java APIs, and a command line API that should all be insensitive to the availability of any specific server or components.  At Yahoo! it is not required that there be session fail-over from the client.  It is acceptable for the client to reconnect if a session is lost as long as the state data managed by the Oozie service is not lost.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira