[
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:
- As per Mona's suggestion, instead of using the {{ServiceDiscovery}} directly
(which would cause Oozie to talk to ZooKeeper everytime the metadata, number of
Oozie servers, etc were accessed, we now use the {{ServiceCache}} object, which
internally uses a ZK watch so that it can cache the info; it can therefore be a
second or two stale -- however, Oozie servers shouldn't be joining and leaving
frequently anyway.
- Fixed a bug that was eating a lot of disk space over time when running unit
tests involving ZK (each method in those test cases was creating a new temp dir
that wasn't being deleted and could quickly reach many GBs)
- Registering and unregistering with {{ZKUtils}} is now synchronized to prevent
a possible race condition with the singleton when starting up Oozie (I didn't
actually run into any issues, this is just a precaution)
- Fixes some incorrect Javadoc comments
> 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, 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
