[OOZIE-615] Support high availability for the Oozie service

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk
• Fix Version/s: 4.1.0
• Component/s: HA
• Assignee: Robert Kanter
• Reporter: Craig Peters
• Created: 23/Nov/11 19:51
• Updated: 09/Dec/14 00:45
• Resolved: 29/Aug/13 18:09

Description

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.

Issue Links

• blocks: AMBARI-6683 Support for Oozie High Availability deployment
• is related to: OOZIE-1460 Implement and Document security for HA
• relates to: OOZIE-1540 When oozie.zookeeper.oozie.id is not specified, its using a space instead of the hostname
• relates to: OOZIE-1561 When using Oozie HA, the logs should also be HA
• relates to: OOZIE-1485 Remove FixedJsonInstanceSerializer.java
• relates to: OOZIE-1560 Log messages should have a way of identifying which server they came from when using HA
• relates to: OOZIE-1491 Make sure HA works with a secure ZooKeeper
• relates to: OOZIE-1492 Make sure HA works with HCat and SLA notifications
• links to: ReviewBoard