Skip to content
Mirror of Apache Oozie
Java JavaScript Shell CSS Batchfile HTML PowerShell
Failed to load latest commit information.
bin OOZIE-1753 Update create-release-artifact script for git (rkanter)
builds OOZIE-1000 Remove Yahoo branding from docs, tests, etc (rkanter via v…
client OOZIE-2346 Add sub-workflow information like the super-parent id and …
core OOZIE-2397 LAST_ONLY and NONE don't properly handle READY actions (rk…
distro OOZIE-2159 'oozie validate' command should be moved server-side (seoe…
docs OOZIE-2397 LAST_ONLY and NONE don't properly handle READY actions (rk…
examples OOZIE-2355 Hive2 Action doesn't pass along oozie configs to jobconf (…
hadooplibs OOZIE-2365 oozie fail to start when smtp password not set (rohini)
login bumped up version to 4.3.0-SNAPSHOT
minitest bumped up version to 4.3.0-SNAPSHOT
sharelib OOZIE-2382 org.apache.oozie.action.hadoop.TestPigMain.testPig_withNul…
src/main OOZIE-2071 Add a Spark example (pavan kumar via rkanter)
tools OOZIE-2272 Use Hadoop's CredentialProvider for passwords in oozie-sit…
utils/dbutils/updatescripts Adding Apache License 2.0 missing sql/pig/js
webapp OOZIE-2251 Expose instrumental matrices in Realtime Graphing tool (np…
workflowgenerator bumped up version to 4.3.0-SNAPSHOT
zookeeper-security-tests bumped up version to 4.3.0-SNAPSHOT
.gitignore OOZIE-1968 Building modules independently (shwethags)
DISCLAIMER.txt OOZIE-683 Add DISCLAIMER file in the root.(Mohammad)
LICENSE.txt OOZIE-685 Update License file with 3rd party license information. (Mo…
NOTICE.txt OOZIE-678 Update NOTICE.txt to reflect the workcount binaries into oo…
README.txt OOZIE-1102 Update Oozie README.txt to have the TLP mailing list and l…
pom.xml OOZIE-2251 Expose instrumental matrices in Realtime Graphing tool (np…
release-log.txt OOZIE-2397 LAST_ONLY and NONE don't properly handle READY actions (rk…
source-headers.txt Adding Apache License 2.0 txt files
work.log Merge pull request #749 from angelokh/OOZIE-97-3.0.1


Apache Oozie

What is Oozie

Oozie is an extensible, scalable and reliable system to define, manage, schedule, and execute complex Hadoop workloads via web services. More specifically, this includes:

  * XML-based declarative framework to specify a job or a complex workflow of dependent jobs.
  * Support different types of job such as Hadoop Map-Reduce, Pipe, Streaming, Pig, Hive and custom java applications.
  * Workflow scheduling based on frequency and/or data availability.
  * Monitoring capability, automatic retry and failure handing of jobs.
  * Extensible and pluggable architecture to allow arbitrary grid programming paradigms.
  * Authentication, authorization, and capacity-aware load throttling to allow multi-tenant software as a service.

Oozie Overview

Oozie is a server based Workflow Engine specialized in running workflow jobs with actions that run Hadoop Map/Reduce and Pig jobs.

Oozie is a Java Web-Application that runs in a Java servlet-container.

For the purposes of Oozie, a workflow is a collection of actions (i.e. Hadoop Map/Reduce jobs, Pig jobs) arranged in a control dependency DAG (Direct Acyclic Graph). "control dependency" from one action to another means that the second action can't run until the first action has completed.

Oozie workflows definitions are written in hPDL (a XML Process Definition Language similar to JBOSS JBPM jPDL).

Oozie workflow actions start jobs in remote systems (i.e. Hadoop, Pig). Upon action completion, the remote systems callback Oozie to notify the action completion, at this point Oozie proceeds to the next action in the workflow.

Oozie workflows contain control flow nodes and action nodes.

Control flow nodes define the beginning and the end of a workflow ( start , end and fail nodes) and provide a mechanism to control the workflow execution path ( decision , fork and join nodes).

Action nodes are the mechanism by which a workflow triggers the execution of a computation/processing task. Oozie provides support for different types of actions: Hadoop map-reduce, Hadoop file system, Pig, SSH, HTTP, eMail and Oozie sub-workflow. Oozie can be extended to support additional type of actions.

Oozie workflows can be parameterized (using variables like ${inputDir} within the workflow definition). When submitting a workflow job values for the parameters must be provided. If properly parameterized (i.e. using different output directories) several identical workflow jobs can concurrently.

Documentations :
Oozie web service is bundle with the built-in details documentation.

More inforamtion could be found at:

Oozie Quick Start:

Supported Hadoop Versions:

This version of Oozie was primarily tested against Hadoop 0.20.205.x. This will not work on earlier versions of Hadoop such as 0.20.x. and 0.21.


If you have any questions/issues, please send an email to:

Subscribe using the link:

Something went wrong with that request. Please try again.