[
https://issues.apache.org/jira/browse/OOZIE-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733619#comment-13733619
]
Rohini Palaniswamy commented on OOZIE-615:
------------------------------------------
Will post code review comments on review board.
Aside form that, we will need separate jiras for
- working with secure zookeeper and sasl acl setting. This prevents some one
else from deleting the oozie related znodes.
- getting hcat integration and SLA notifications to work. Both have in-memory
datastructures and HA will impact them.
- Log streaming does not work with secure Oozie server. Mona found this when
she was trying out HA.
> 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
