[[index][::Go back to Oozie Documentation Index::]] ----- ---+!! Oozie Specification, a Hadoop Workflow System *
(PROPOSAL v1.0-2009MAY21)
* The goal of this document is to define a workflow engine system specialized in coordinating the execution of Hadoop Map/Reduce and Pig jobs. Author: Alejandro Abdelnur %TOC% ---++ Changelog ---+++!! 2010APR27 * #3.2.3 Added new "arguments" tag to PIG actions * #3.2.5 SSH actions are deprecated in Oozie schema 0.1 and removed in Oozie schema 0.2 * #Appendix A, Added schema version 0.2 ---+++!! 2009OCT20 * #Appendix A, updated XML schema ---+++!! 2009SEP15 * #3.2.6 Removing support for sub-workflow in a different Oozie instance (removing the 'oozie' element) ---+++!! 2009SEP07 * #3.2.2.3 Added Map Reduce Pipes specifications. * #3.2.2.4 Map-Reduce Examples. Previously was 3.2.2.3. ---+++!! 2009SEP02 * #10 Added missing skip nodes property name. * #3.2.1.4 Reworded action recovery explanation. ---+++!! 2009AUG26 * #3.2.9 Added =java= action type * #3.1.4 Example uses EL constant to refer to counter group/name ---+++!! 2009JUN09 * #12.2.4 Added build version resource to admin end-point * #3.2.6 Added flag to propagate workflow configuration to sub-workflows * #10 Added behavior for workflow job parameters given in the rerun * #11.3.4 workflows info returns pagination information ---+++!! 2009MAY18 * #3.1.4 decision node, 'default' element, 'name' attribute changed to 'to' * #3.1.5 fork node, 'transition' element changed to 'start', 'to' attribute change to 'path' * #3.1.5 join node, 'transition' element remove, added 'to' attribute to 'join' element * #3.2.1.4 Rewording on action recovery section * #3.2.2 map-reduce action, added 'job-tracker', 'name-node' actions, 'file', 'file' and 'archive' elements * #3.2.2.1 map-reduce action, remove from 'streaming' element 'file', 'file' and 'archive' elements * #3.2.2.2 map-reduce action, reorganized streaming section * #3.2.3 pig action, removed information about implementation (SSH), changed elements names * #3.2.4 fs action, removed 'fs-uri' and 'user-name' elements, file system URI is now specified in path, user is propagated * #3.2.6 sub-workflow action, renamed elements 'oozie-url' to 'oozie' and 'workflow-app' to 'app-path' * #4 Properties that are valid Java identifiers can be used as ${NAME} * #4.1 Renamed default properties file from 'configuration.xml' to 'default-configuration.xml' * #4.2 Changes in EL Constants and Functions * #5 Updated notification behavior and tokens * #6 Changed user propagation behavior * #7 Changed application packaging from ZIP to HDFS directory * Removed application lifecycle and self containment model sections * #10 Changed workflow job recovery, simplified recovery behavior * #11 Detailed Web Services API * #12 Updated Client API section * #15 Updated Action Executor API section * #Appendix A XML namespace updated to 'uri:oozie:workflow:0.1' * #Appendix A Updated XML schema to changes in map-reduce/pig/fs/ssh actions * #Appendix B Updated workflow example to schema changes ---+++!! 2009MAR25 * Changing all references of HWS to Oozie (project name) * Typos, XML Formatting * XML Schema URI correction ---+++!! 2009MAR09 * Changed =CREATED= job state to =PREP= to have same states as Hadoop * Renamed 'hadoop-workflow' element to 'workflow-app' * Decision syntax changed to be 'switch/case' with no transition indirection * Action nodes common root element 'action', with the action type as sub-element (using a single built-in XML schema) * Action nodes have 2 explicit transitions 'ok to' and 'error to' enforced by XML schema * Renamed 'fail' action element to 'kill' * Renamed 'hadoop' action element to 'map-reduce' * Renamed 'hdfs' action element to 'fs' * Updated all XML snippets and examples * Made user propagation simpler and consistent * Added Oozie XML schema to Appendix A * Added workflow example to Appendix B ---+++!! 2009FEB22 * Opened [[https://issues.apache.org/jira/browse/HADOOP-5303][JIRA HADOOP-5303]] ---++ 0 Definitions *Action:* An execution/computation task (Map-Reduce job, Pig job, a shell command). It can also be referred as task or 'action node'. *Workflow:* A collection of actions 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. *Workflow Definition:* A programmatic description of a workflow that can be executed. *Workflow Definition Language:* The language used to define a Workflow Definition. *Workflow Job:* An executable instance of a workflow definition. *Workflow Engine:* A system that executes workflows jobs. It can also be referred as a DAG engine. ---++ 1 Specification Highlights A Workflow application is DAG that coordinates the following types of actions: Hadoop, Pig, and sub-workflows. Flow control operations within the workflow applications can be done using decision, fork and join nodes. Cycles in workflows are not supported. Actions and decisions can be parameterized with job properties, actions output (i.e. Hadoop counters) and file information (file exists, file size, etc). Formal parameters are expressed in the workflow definition as =${VAR}= variables. A Workflow application is a ZIP file that contains the workflow definition (an XML file), all the necessary files to run all the actions: JAR files for Map/Reduce jobs, shells for streaming Map/Reduce jobs, native libraries, Pig scripts, and other resource files. Before running a workflow job, the corresponding workflow application must be deployed in Oozie. Deploying workflow application and running workflow jobs can be done via command line tools, a WS API and a Java API. Monitoring the system and workflow jobs can be done via a web console, command line tools, a WS API and a Java API. When submitting a workflow job, a set of properties resolving all the formal parameters in the workflow definitions must be provided. This set of properties is a Hadoop configuration. Possible states for a workflow jobs are: =PREP=, =RUNNING=, =SUSPENDED=, =SUCCEEDED=, =KILLED= and =FAILED=. In the case of a action start failure in a workflow job, depending on the type of failure, Oozie will attempt automatic retries, it will request a manual retry or it will fail the workflow job. Oozie can make HTTP callback notifications on action start/end/failure events and workflow end/failure events. In the case of workflow job failure, the workflow job can be resubmitted skipping previously completed actions. Before doing a resubmission the workflow application could be updated with a patch to fix a problem in the workflow application code. #WorkflowDefinition ---++ 2 Workflow Definition A workflow definition is a DAG with control flow nodes (start, end, decision, fork, join, kill) or action nodes (map-reduce, pig, etc.), nodes are connected by transitions arrows. The workflow definition language is XML based and it is called hPDL (Hadoop Process Definition Language). Refer to the Appendix A for the[[WorkflowFunctionalSpec#OozieWFSchema][Oozie Workflow Definition XML Schema]]. Appendix B has [[WorkflowFunctionalSpec#OozieWFExamples][Workflow Definition Examples]]. ---++ 2.1 Cycles in Workflow Definitions Oozie does not support cycles in workflow definitions, workflow definitions must be a strict DAG. At workflow application deployment time, if Oozie detects a cycle in the workflow definition it must fail the deployment. ---++ 3 Workflow Nodes Workflow nodes are classified in control flow nodes and action nodes: * *Control flow nodes:* nodes that control the start and end of the workflow and workflow job execution path. * *Action nodes:* nodes that trigger the execution of a computation/processing task. Node names and transitions must be conform to the following pattern =[a-zA-Z][\-_a-zA-Z0-0]*=, of up to 20 characters long. ---+++ 3.1 Control Flow Nodes Control flow nodes define the beginning and the end of a workflow (the =start=, =end= and =kill= nodes) and provide a mechanism to control the workflow execution path (the =decision=, =fork= and =join= nodes). #StartNode ---++++ 3.1.1 Start Control Node The =start= node is the entry point for a workflow job, it indicates the first workflow node the workflow job must transition to. When a workflow is started, it automatically transitions to the node specified in the =start=. A workflow definition must have one =start= node. *Syntax:* ... ... The =to= attribute is the name of first workflow node to execute. *Example:* ... ... #EndNode ---++++ 3.1.2 End Control Node The =end= node is the end for a workflow job, it indicates that the workflow job has completed successfully. When a workflow job reaches the =end= it finishes successfully (SUCCEEDED). If one or more actions started by the workflow job are executing when the =end= node is reached, the actions will be killed. In this scenario the workflow job is still considered as successfully run. A workflow definition must have one =end= node. *Syntax:* ... ... The =name= attribute is the name of the transition to do to end the workflow job. *Example:* ... #KillNode ---++++ 3.1.3 Kill Control Node The =kill= node allows a workflow job to kill itself. When a workflow job reaches the =kill= it finishes in error (KILLED). If one or more actions started by the workflow job are executing when the =kill= node is reached, the actions will be killed. A workflow definition may have zero or more =kill= nodes. *Syntax:* ... [MESSAGE-TO-LOG] ... The =name= attribute in the =kill= node is the name of the Kill action node. The content of the =message= element will be logged as the kill reason for the workflow job. A =kill= node does not have transition elements because it ends the workflow job, as =KILLED=. *Example:* ... Input unavailable ... #DecisionNode ---++++ 3.1.4 Decision Control Node A =decision= node enables a workflow to make a selection on the execution path to follow. The behavior of a =decision= node can be seen as a switch-case statement. A =decision= node consists of a list of predicates-transition pairs plus a default transition. Predicates are evaluated in order or appearance until one of them evaluates to =true= and the corresponding transition is taken. If none of the predicates evaluates to =true= the =default= transition is taken. Predicates are JSP Expression Language (EL) expressions (refer to section 4.2 of this document) that resolve into a boolean value, =true= or =false=. For example: ${wf:nodeStatus('myfirstjob') == 'OK'} ${fs:size('/usr/foo/myinputdir') gt 10 * GB} *Syntax:* ... [PREDICATE] ... [PREDICATE] ... The =name= attribute in the =decision= node is the name of the decision node. Each =case= elements contains a predicate an a transition name. The predicate ELs are evaluated in order until one returns =true= and the corresponding transition is taken. The =default= element indicates the transition to take if none of the predicates evaluates to =true=. All decision nodes must have a =default= element to avoid bringing the workflow into an error state if none of the predicates evaluates to true. *Example:* ... ${fs:size(secondjobOutputDir) gt 10 * GB} ${fs:size(secondjobOutputDir) lt 100 * MB} ${ hadoop:counters('secondjob')[RECORDS][REDUCE_OUT] lt 1000000 } ... #ForkJoinNodes ---++++ 3.1.5 Fork and Join Control Nodes A =fork= node splits one path of execution into multiple concurrent paths of execution. A =join= node waits until every concurrent execution path of a previous =fork= node arrives to it. The =fork= and =join= nodes must be used in pairs. The =join= node assumes concurrent execution paths are children of the same =fork= node. *Syntax:* ... ... ... ... The =name= attribute in the =fork= node is the name of the workflow fork node. The =start= attribute in the =path= elements in the =fork= node indicate the name of the workflow node that will be part of the concurrent execution paths. The =name= attribute in the =join= node is the name of the workflow join node. The =to= attribute in the =join= node indicates the name of the workflow node that will executed after all concurrent execution paths of the corresponding fork arrive to the join node. *Example:* ... foo:9001 bar:9000 job1.xml foo:9001 bar:9000 job2.xml ... #ActionNodes ---+++ 3.2 Workflow Action Nodes Action nodes are the mechanism by which a workflow triggers the execution of a computation/processing task. ---++++ 3.2.1 Action Basis The following sub-sections define common behavior and capabilities for all action types. ---+++++ 3.2.1.1 Action Computation/Processing Is Always Remote All computation/processing tasks triggered by an action node are remote to Oozie. No workflow application specific computation/processing task is executed within Oozie. ---+++++ 3.2.1.2 Actions Are Asynchronous All computation/processing tasks triggered by an action node are executed asynchronously by Oozie. For most types of computation/processing tasks triggered by workflow action, the workflow job has to wait until the computation/processing task completes before transitioning to the following node in the workflow. The exception is the =fs= action that is handled as a synchronous action. Oozie can detect completion of computation/processing tasks by two different means, callbacks and polling. When a computation/processing tasks is started by Oozie, Oozie provides a unique callback URL to the task, the task should invoke the given URL to notify its completion. For cases that the task failed to invoke the callback URL for any reason (i.e. a transient network failure) or when the type of task cannot invoke the callback URL upon completion, Oozie has a mechanism to poll computation/processing tasks for completion. ---+++++ 3.2.1.3 Actions Have 2 Transitions, =ok= and =error= If a computation/processing task -triggered by a workflow- completes successfully, it transitions to =ok=. If a computation/processing task -triggered by a workflow- fails to complete successfully, its transitions to =error=. If a computation/processing task exits in error, there computation/processing task must provide =error-code= and =error-message= information to Oozie. This information can be used from =decision= nodes to implement a fine grain error handling at workflow application level. Each action type must clearly define all the error codes it can produce. ---+++++ 3.2.1.4 Action Recovery Oozie provides recovery capabilities when starting or ending actions. Once an action starts successfully Oozie will not retry starting the action if the action fails during its execution. The assumption is that the external system (i.e. Hadoop) executing the action has enough resilience to recovery jobs once it has started (i.e. Hadoop task retries). Depending on the nature of the failure, Oozie will have different recovery strategies. If the failure is of transient nature, Oozie will perform retries after a pre-defined time interval. The number of retries and timer interval for a type of action must be pre-configured at Oozie level. Workflow jobs can override such configuration. Examples of a transient failures are network problems or a remote system temporary unavailable. If the failure is of non-transient nature, Oozie will suspend the workflow job until an manual or programmatic intervention resumes the workflow job and the action start or end is retried. It is the responsibility of an administrator or an external managing system to perform any necessary cleanup before resuming the workflow job. If the failure is an error and a retry will not resolve the problem, Oozie will perform the error transition for the action. #MapReduceAction ---++++ 3.2.2 Map-Reduce Action The =map-reduce= action starts a Hadoop map/reduce job from a workflow. Hadoop jobs can be Java Map/Reduce jobs or streaming jobs. A =map-reduce= action can be configured to perform file system cleanup and directory creation before starting the map reduce job. This capability enables Oozie to retry a Hadoop job in the situation of a transient failure (Hadoop checks the non-existence of the job output directory and then creates it when the Hadoop job is starting, thus a retry without cleanup of the job output directory would fail). The workflow job will wait until the Hadoop map/reduce job completes before continuing to the next action in the workflow execution path. The counters of the Hadoop job and job exit status (=FAILED=, =KILLED= or =SUCCEEDED=) must be available to the workflow job after the Hadoop jobs ends. This information can be used from within decision nodes and other actions configurations. The =map-reduce= action has to be configured with all the necessary Hadoop JobConf properties to run the Hadoop map/reduce job. Hadoop JobConf properties can be specified in a JobConf XML file bundled with the workflow application or they can be indicated inline in the =map-reduce= action configuration. The configuration properties are loaded in the following order, =streaming=, =job-xml= and =configuration=, and later values override earlier values. Streaming and inline property values can be parameterized (templatized) using EL expressions. The Hadoop =mapred.job.tracker= and =fs.default.name= properties must not be present in the job-xml and inline configuration. #FilesAchives ---++++ 3.2.2.1 Adding Files and Archives for the Job The =file=, =archive= elements make available, to map-reduce jobs, files and archives. If the specified path is relative, it is assumed the file or archiver are within the application directory, in the corresponding sub-path. If the path is absolute, the file or archive it is expected in the given absolute path. Files specified with the =file= element, will be symbolic links in the home directory of the task. If a file is a native library (an '.so' or a '.so.#' file), it will be symlinked as and '.so' file in the task running directory, thus available to the task JVM. To force a symlink for a file on the task running directory, use a '#' followed by the symlink name. For example 'mycat.sh#cat'. Refer to Hadoop distributed cache documentation for details more details on files and archives. #StreamingMapReduceAction ---+++++ 3.2.2.2 Streaming Streaming information can be specified in the =streaming= element. The =mapper= and =reducer= elements are used to specify the executable/script to be used as mapper and reducer. User defined scripts must be bundled with the workflow application and they must be declared in the =files= element of the streaming configuration. If the are not declared in the =files= element of the configuration it is assumed they will be available (and in the command PATH) of the Hadoop slave machines. Some streaming jobs require Files found on HDFS to be available to the mapper/reducer scripts. This is done using the =file= and =archive= elements described in the previous section. The Mapper/Reducer can be overridden by a =mapred.mapper.class= or =mapred.reducer.class= properties in the =job-xml= file or =configuration= elements. #PipesMapReduceAction ---+++++ 3.2.2.3 Pipes Pipes information can be specified in the =pipes= element. A subset of the command line options which can be used while using the Hadoop Pipes Submitter can be specified via elements - =map=, =reduce=, =inputformat=, =partitioner=, =writer=, =program=. The =program= element is used to specify the executable/script to be used. User defined program must be bundled with the workflow application. Some pipe jobs require Files found on HDFS to be available to the mapper/reducer scripts. This is done using the =file= and =archive= elements described in the previous section. Pipe properties can be overridden by specifying them in the =job-xml= file or =configuration= element. ---+++++ 3.2.2.4 Syntax ... [JOB-TRACKER] [NAME-NODE] ... ... [MAPPER-PROCESS] [REDUCER-PROCESS] [RECORD-READER-CLASS] [NAME=VALUE] ... [NAME=VALUE] ... [MAPPER] [REDUCER] [INPUTFORMAT] [PARTITIONER] [OUTPUTFORMAT] [EXECUTABLE] [JOB-XML-FILE] [PROPERTY-NAME] [PROPERTY-VALUE] ... [FILE-PATH] ... [FILE-PATH] ... ... The =prepare= element, if present, indicates a list of path do delete before starting the job. This should be used exclusively for directory cleanup for the job to be executed. The delete operation will be performed in the =fs.default.name= filesystem. The =job-xml= element, if present, must refer to a Hadoop JobConf =job.xml= file bundled in the workflow application. The =job-xml= element is optional and if present it can be only one. The =configuration= element, if present, contains JobConf properties for the Hadoop job. Properties specified in the =configuration= element override properties specified in the file specified in the =job-xml= element. The =file= element, if present, must specify the target sybolic link for binaries by separating the original file and target with a # (file#target-sym-link). This is not required for libraries. The =mapper= and =reducer= process for streaming jobs, should specify the executable command with URL encoding. e.g. '%' should be replaced by '%25'. *Example:* ... foo:9001 bar:9000 /myfirstjob.xml mapred.input.dir /usr/tucu/input-data mapred.output.dir /usr/tucu/input-data mapred.reduce.tasks ${firstJobReducers} ... In the above example, the number of Reducers to be used by the Map/Reduce job has to be specified as a parameter of the workflow job configuration when creating the workflow job. *Streaming Example:* ... foo:9001 bar:9000 /bin/bash testarchive/bin/mapper.sh testfile /bin/bash testarchive/bin/reducer.sh mapred.input.dir ${input} mapred.output.dir ${output} stream.num.map.output.key.fields 3 /users/blabla/testfile.sh#testfile /users/blabla/testarchive.jar#testarchive ... *Pipes Example:* ... foo:9001 bar:9000 bin/wordcount-simple#wordcount-simple mapred.input.dir ${input} mapred.output.dir ${output} /users/blabla/testarchive.jar#testarchive ... #PigAction ---++++ 3.2.3 Pig Action The =pig= action starts a Pig job. The workflow job will wait until the pig job completes before continuing to the next action. The =pig= action has to be configured with the job-tracker, name-node, pig script and the necessary parameters and configuration to run the Pig job. A =pig= action can be configured to perform HDFS files/directories cleanup before starting the Pig job. This capability enables Oozie to retry a Pig job in the situation of a transient failure (Pig creates temporary directories for intermediate data, thus a retry without cleanup would fail). Hadoop JobConf properties can be specified in a JobConf XML file bundled with the workflow application or they can be indicated inline in the =pig= action configuration. The configuration properties are loaded in the following order, =job-xml= and =configuration=, and later values override earlier values. Inline property values can be parameterized (templatized) using EL expressions. The Hadoop =mapred.job.tracker= and =fs.default.name= properties must not be present in the job-xml and inline configuration. As with Hadoop map-reduce jobs, it is possible to add files and archives to be available to the Pig job, refer to section [#FilesAchives][Adding Files and Archives for the Job]. *Syntax for Pig actions in Oozie schema 0.2:* ... [JOB-TRACKER] [NAME-NODE] ... ... [JOB-XML-FILE] [PROPERTY-NAME] [PROPERTY-VALUE] ... [PARAM-VALUE] ... [PARAM-VALUE] [ARGUMENT-VALUE] ... [ARGUMENT-VALUE] [FILE-PATH] ... [FILE-PATH] ... ... *Syntax for Pig actions in Oozie schema 0.1:* ... [JOB-TRACKER] [NAME-NODE] ... ... [JOB-XML-FILE] [PROPERTY-NAME] [PROPERTY-VALUE] ... [PARAM-VALUE] ... [PARAM-VALUE] [FILE-PATH] ... [FILE-PATH] ... ... The =prepare= element, if present, indicates a list of path do delete before starting the job. This should be used exclusively for directory cleanup for the job to be executed. The =job-xml= element, if present, must refer to a Hadoop JobConf =job.xml= file bundled in the workflow application. The =job-xml= element is optional and if present it can be only one. The =configuration= element, if present, contains JobConf properties for the underlying Hadoop jobs. Properties specified in the =configuration= element override properties specified in the file specified in the =job-xml= element. The inline and job-xml configuration properties are passed to the Hadoop jobs submitted by Pig runtime. The =script= element contains the pig script to execute. The pig script can be templatized with variables of the form =${VARIABLE}=. The values of these variables can then be specified using the =params= element. NOTE: Oozie will perform the parameter substitution before firing the pig job. This is different from the [[http://wiki.apache.org/pig/ParameterSubstitution][parameter substitution mechanism provided by Pig]], which has a few limitations. The =params= element, if present, contains parameters to be passed to the pig script. *In Oozie schema 0.2:* The =arguments= element, if present, contains arguments to be passed to the pig script. All the above elements can be parameterized (templatized) using EL expressions. *Example for Oozie schema 0.2:* ... foo:9001 bar:9000 mapred.compress.map.output true -param INPUT=${inputDir} -param OUTPUT=${outputDir}/pig-output3 ... *Example for Oozie schema 0.1:* ... foo:9001 bar:9000 mapred.compress.map.output true InputDir=/home/tucu/input-data OutputDir=${jobOutput} ... #FsAction ---++++ 3.2.4 Fs (HDFS) action The =fs= action allows to manipulate files and directories in HDFS from a workflow application. The supported commands are =move=, =delete= and =mkdir=. The FS commands are executed synchronously from within the FS action, the workflow job will wait until the specified file commands are completed before continuing to the next action. Path names specified in the =fs= action can be parameterized (templatized) using EL expressions. Each file path must specify the file system URI, for move operations, the target must not specified the system URI. IMPORTANT: All the commands within =fs= action do not happen atomically, if a =fs= action fails half way in the commands being executed, successfully executed commands are not rolled back. The =fs= action, before executing any command must check that source paths exist and target paths don't exist, thus failing before executing any command. Therefore the validity of all paths specified in one =fs= action are evaluated before any of the file operation are executed. Thus there is less chance of an error occurring while the =fs= action executes. *Syntax:* ... ... ... ... ... The =delete= command deletes the specified path, if it is a directory it deletes recursively all its content and then deletes the directory. The =mkdir= command creates the specified directory, it creates all missing directories in the path. If the directory already exist it does a no-op. In the =move= command the =source= path must exist and the =target= path must not exist. The parent directory of the =target= path must exist, the =target= path must not specify the file system URI. The =chmod= command changes the permissions for the specified path. Permissions can be specified using the Unix Symbolic representation (e.g. -rwxrw-rw-) or an octal representation (755). When doing a =chmod= command on a directory, by default the command is applied to the directory and the files one level within the directory. To apply the =chmod= command to the directory, without affecting the files within it, the =dir-files= attribute must be set to =false=. If relative paths are used it will be relative to the specified user home directory. *Example:* ... true ... In the above example, a directory named after the workflow job ID is created and the input of the job, passed as workflow configuration parameter, is archived under the previously created directory. #SshAction ---++++ 3.2.5 Ssh Action *NOTE: SSH actions are deprecated in Oozie schema 0.1, and removed in Oozie schema 0.2* The =ssh= action starts a shell command on a remote machine as a remote secure shell in background. The workflow job will wait until the remote shell command completes before continuing to the next action. The shell command must be present in the remote machine and it must be available for execution via the command path. The shell command is executed in the home directory of the specified user in the remote host. The output (STDOUT) of the ssh job can be made available to the workflow job after the ssh job ends. This information could be used from within decision nodes. If the output of the ssh job is made available to the workflow job the shell command must follow the following requirements: * The format of the output must be a valid Java Properties file. * The size of the output must not exceed 2KB. *Syntax:* ... [USER]@[HOST] [SHELL] [ARGUMENTS] ... ... The =host= indicates the user and host where the shell will be executed. The =command= element indicates the shell command to execute. The =args= element, if present, contains parameters to be passed to the shell command. If more than one =args= element is present they are concatenated in order. If the =capture-output= element is present, it indicates Oozie to capture output of the STDOUT of the ssh command execution. The ssh command output must be in Java Properties file format and it must not exceed 2KB. From within the workflow definition, the output of an ssh action node is accessible via the =String action:output(String node, String key)= function (Refer to section '4.2.6 Action EL Functions'). The configuration of the =ssh= action can be parameterized (templatized) using EL expressions. *Example:* ... foo@bar.com uploaddata jdbc:derby://bar.com:1527/myDB hdfs://foobar.com:9000/usr/tucu/myData ... In the above example, the =uploaddata= shell command is executed with two arguments, =jdbc:derby://foo.com:1527/myDB= and =hdfs://foobar.com:9000/usr/tucu/myData=. The =uploaddata= shell must be available in the remote host and available in the command path. The output of the command will be ignored because the =capture-output= element is not present. #SubWorkflowAction ---++++ 3.2.6 Sub-workflow Action The =sub-workflow= action runs a child workflow job, the child workflow job can be in the same Oozie system or in another Oozie system. The parent workflow job will wait until the child workflow job has completed. *Syntax:* ... [WF-APPLICATION-PATH] [PROPERTY-NAME] [PROPERTY-VALUE] ... ... The child workflow job runs in the same Oozie system instance where the parent workflow job is running. The =app-path= element specifies the path to the workflow application of the child workflow job. The =propagate-configuration= flag, if present, indicates that the workflow job configuration should be propagated to the child workflow. The =configuration= section can be used to specify the job properties that are required to run the child workflow job. The configuration of the =sub-workflow= action can be parameterized (templatized) using EL expressions. *Example:* ... child-wf input.dir ${wf:id()}/second-mr-output ... In the above example, the workflow definition with the name =child-wf= will be run on the Oozie instance at =.http://myhost:8080/oozie=. The specified workflow application must be already deployed on the target Oozie instance. A configuration parameter =input.dir= is being passed as job property to the child workflow job. #JavaAction ---++++ 3.2.7 Java Action The =java= action will execute the =public static void main(String[] args)= method of the specified main Java class. Java applications are executed in the Hadoop cluster as map-reduce job with a single Mapper task. The workflow job will wait until the java application completes its execution before continuing to the next action. The =java= action has to be configured with the job-tracker, name-node, main Java class, JVM options and arguments. To indicate an =ok= action transition, the main Java class must complete gracefully the =main= method invocation. To indicate an =error= action transition, the main Java class must throw an exception. The main Java class must not call =System.exit(int n)= as this will make the =java= action to do an =error= transition regardless of the used exit code. A =java= action can be configured to perform HDFS files/directories cleanup before starting the Java application. This capability enables Oozie to retry a Java application in the situation of a transient or non-transient failure (This can be used to cleanup any temporary data which may have been created by the Java application in case of failure). A =java= action can create a Hadoop configuration. The Hadoop configuration is made available as a local file to the Java application in its running directory, the file name is =oozie-action.conf.xml=. Similar to =map-reduce= and =pig= actions it is possible to refer a =job.xml= file and using inline configuration properties. For repeated configuration properties later values override earlier ones. Inline property values can be parameterized (templatized) using EL expressions. The Hadoop =mapred.job.tracker= (=job-tracker=) and =fs.default.name= (=name-node=) properties must not be present in the =job-xml= and in the inline configuration. As with =map-reduce= and =pig= actions, it is possible to add files and archives to be available to the Java application. Refer to section [#FilesAchives][Adding Files and Archives for the Job]. The =capture-output= element can be used to propagate values back into Oozie context, which can then be accessed via EL-functions. This needs to be written out as a java properties format file. The filename is obtained via a System property specified by the constant =JavaMainMapper.OOZIE_JAVA_MAIN_CAPTURE_OUTPUT_FILE= *IMPORTANT:* Because the Java application is run from within a Map-Reduce job, from Hadoop 0.20. onwards a queue must be assigned to it. The queue name must be specified as a configuration property. *Syntax:* ... [JOB-TRACKER] [NAME-NODE] ... ... [JOB-XML] [PROPERTY-NAME] [PROPERTY-VALUE] ... [MAIN-CLASS] [JAVA-STARTUP-OPTS] ARGUMENT ... [FILE-PATH] ... [FILE-PATH] ... ... The =prepare= element, if present, indicates a list of path do delete before starting the Java application. This should be used exclusively for directory cleanup for the Java application to be executed. The =java-opts= element, if present, contains the command line parameters which are to be used to start the JVM that will execute the Java application. Using this element is equivalent to use the =mapred.child.java.opts= configuration property. The =arg= elements, if present, contains arguments for the main function. The value of each =arg= element is considered a single argument and they are passed to the =main= method in the same order. All the above elements can be parameterized (templatized) using EL expressions. *Example:* ... foo:9001 bar:9000 mapred.queue.name default org.apache.oozie.MyFirstMainClass -Dblah argument1 argument2 ... #WorkflowParameterization ---++ 4 Parameterization of Workflows Workflow definitions can be parameterized. When workflow node is executed by Oozie all the ELs are resolved into concrete values. The parameterization of workflow definitions it done using JSP Expression Language syntax from the [[http://jcp.org/aboutJava/communityprocess/final/jsr152/][JSP 2.0 Specification (JSP.2.3)]], allowing not only to support variables as parameters but also functions and complex expressions. EL expressions can be used in the configuration values of action and decision nodes. They can be used in XML attribute values and in XML element and attribute values. They cannot be used in XML element and attribute names. They cannot be used in the name of a node and they cannot be used within the =transition= elements of a node. #WorkflowProperties ---+++ 4.1 Workflow Job Properties (or Parameters) When a workflow job is submitted to Oozie, the submitter may specify as many workflow job properties as required (similar to Hadoop JobConf properties). Workflow applications may define default values for the workflow job parameters. They must be defined in a =config-default.xml= file bundled with the workflow application archive (refer to section '7 Workflow Applications Packaging'). Workflow job properties have precedence over the default values. Properties that are a valid Java identifier, [A-Za-z_][0-9A-Za-z_]*, are available as '${NAME}' variables within the workflow definition. Properties that are not valid Java Identifier, for example 'job.tracker', are available via the =String wf:conf(String name)= function. Valid identifier properties are available via this function as well. Using properties that are valid Java identifiers result in a more readable and compact definition. By using properties *Example:* Parameterized Workflow definition: ... ${jobTracker} ${nameNode} mapred.mapper.class com.foo.FirstMapper mapred.reducer.class com.foo.FirstReducer mapred.input.dir ${inputDir} mapred.output.dir ${outputDir} ... When submitting a workflow job for the workflow definition above, 3 workflow job properties must be specified: * =jobTracker:= * =inputDir:= * =outputDir:= #WorkflowELSupport ---+++ 4.2 Expression Language Functions Oozie, besides allowing the use of workflow job properties to parameterize workflow jobs, it provides a set of build in EL functions that enable a more complex parameterization of workflow action nodes as well as the predicates in decision nodes. ---++++ 4.2.1 Basic EL Constants * *KB:* 1024, one kilobyte. * *MB:* 1024 * KB, one megabyte. * *GB:* 1024 * MB, one gigabyte. * *TB:* 1024 * GB, one terabyte. * *PB:* 1024 * TG, one petabyte. All the above constants are of type =long=. ---++++ 4.2.2 Basic EL Functions *String firstNotNull(String value1, String value2)* It returns the first not =null= value, or =null= if both are =null=. Note that if the output of this function is =null= and it is used as string, the EL library converts it to an empty string. This is the common behavior when using =firstNotNull()= in node configuration sections. *String concat(String s1, String s2)* It returns the concatenation of 2 strings. A string with =null= value is considered as an empty string. *String trim(String s)* It returns the trimmed value of the given string. A string with =null= value is considered as an empty string. *String urlEncode(String s)* It returns the URL UTF-8 encoded value of the given string. A string with =null= value is considered as an empty string. *String timestamp()* It returns the UTC current date and time in W3C format down to the second (YYYY-MM-DDThh:mm:ss.sZ). I.e.: 1997-07-16T19:20:30.45Z ---++++ 4.2.3 Workflow EL Functions *String wf:id()* It returns the workflow job ID for the current workflow job. *String wf:name()* It returns the workflow application name for the current workflow job. *String wf:appPath()* It returns the workflow application path for the current workflow job. *String wf:conf(String name)* It returns the value of the workflow job configuration property for the current workflow job, or an empty string if undefined. *String wf:user()* It returns the user name that started the current workflow job. *String wf:group()* It returns the group name for the current workflow job. *String wf:callback(String stateVar)* It returns the callback URL for the current workflow action node, =stateVar= can be a valid exit state (=OK= or =ERROR=) for the action or a token to be replaced with the exit state by the remote system executing the task. *String wf:transition(String node)* It returns the transition taken by the specified workflow action node, or an empty string if the action has not being executed or it has not completed yet. *String wf:lastErrorNode()* It returns the name of the last workflow action node that exit with an =ERROR= exit state, or an empty string if no a ction has exited with =ERROR= state in the current workflow job. *String wf:errorCode(String node)* It returns the error code for the specified action node, or an empty string if the action node has not exited with =ERROR= state. Each type of action node must define its complete error code list. *String wf:errorMessage(String message)* It returns the error message for the specified action node, or an empty string if no action node has not exited with =ERROR= state. The error message can be useful for debugging and notification purposes. *int wf:run()* It returns the run number for the current workflow job, normally =0= unless the workflow job is re-run, in which case indicates the current run. *Map wf:actionData(String node)* This function is only applicable to action nodes that produce output data on completion. The output data is in a Java Properties format and via this EL function it is available as a =Map=. *int wf:actionExternalId(String node)* It returns the external Id for an action node, or an empty string if the action has not being executed or it has not completed yet. *int wf:actionTrackerUri(String node)* It returns the tracker URIfor an action node, or an empty string if the action has not being executed or it has not completed yet. *int wf:actionExternalStatus(String node)* It returns the external status for an action node, or an empty string if the action has not being executed or it has not completed yet. ---++++ 4.2.4 Hadoop EL Constants * *RECORDS:* Hadoop record counters group name. * *MAP_IN:* Hadoop mapper input records counter name. * *MAP_OUT:* Hadoop mapper output records counter name. * *REDUCE_IN:* Hadoop reducer input records counter name. * *REDUCE_OUT:* Hadoop reducer input record counter name. * *GROUPS:* 1024 * Hadoop mapper/reducer record groups counter name. ---++++ 4.2.5 Hadoop EL Functions *Map < String, Map < String, Long > > hadoop:counters(String node)* It returns the counters for a job submitted by a Hadoop action node. It returns =0= if the if the Hadoop job has not started yet and for undefined counters. The outer Map key is a counter group name. The inner Map value is a Map of counter names and counter values. The Hadoop EL constants defined in the previous section provide access to the Hadoop built in record counters. ---++++ 4.2.6 HDFS EL Functions For all the functions in this section the path must include the FS URI. For example =hdfs://foo:9000/user/tucu=. *boolean fs:exists(String path)* It returns =true= or =false= depending if the specified path URI exists or not. *boolean fs:isDir(String path)* It returns =true= if the specified path URI exists and it is a directory, otherwise it returns =false=. *boolean fs:dirSize(String path)* It returns the size in bytes of all the files in the specified path. If the path is not a directory, or if it does not exist it returns -1. It does not work recursively, only computes the size of the files under the specified path. *boolean fs:fileSize(String path)* It returns the size in bytes of specified file. If the path is not a file, or if it does not exist it returns -1. *boolean fs:blockSize(String path)* It returns the block size in bytes of specified file. If the path is not a file, or if it does not exist it returns -1. #WorkflowNotifications ---++ 5 Oozie Notifications Workflow jobs can be configured to make an HTTP GET notification upon start and end of a workflow action node and upon the completion of a workflow job. Oozie will make a best effort to deliver the notifications, in case of failure it will retry the notification a pre-configured number of times at a pre-configured interval before giving up. ---+++ 5.1 Workflow Job Status Notification If the =oozie.wf.workflow.notification.url= property is present in the workflow job properties when submitting the job, Oozie will make a notification to the provided URL when the workflow job changes its status. If the URL contains any of the following tokens, they will be replaced with the actual values by Oozie before making the notification: * =$jobId= : The workflow job ID * =$status= : the workflow current state ---+++ 5.2 Node Start and End Notifications If the =oozie.wf.action.notification.url= property is present in the workflow job properties when submitting the job, Oozie will make a notification to the provided URL every time the workflow job enters and exits an action node. For decision nodes, Oozie will send a single notification with the name of the first evaluation that resolved to =true=. If the URL contains any of the following tokens, they will be replaced with the actual values by Oozie before making the notification: * =$jobId= : The workflow job ID * =$nodeName= : The name of the workflow node * =$status= : If the action has not completed yet, it contains the action status 'S:'. If the action has ended, it contains the action transition 'T:' #UserPropagation ---++ 6 User Propagation When submitting a workflow job, the configuration must contain a =user.name= property. If security is enabled, Oozie must ensure that the value of the =user.name= property in the configuration match the user credentials present in the protocol (web services) request. When submitting a workflow job, the configuration may contain a =group.name= property. If security is enabled, Oozie must ensure that the user of the request belongs to the specified group. The specified user and group names are assigned to the created job. Oozie must propagate the specified user and group to the system executing the actions. It is not allowed for map-reduce, pig and fs actions to override user/group information. #AppDeployment ---++ 7 Workflow Application Deployment While Oozie encourages the use of self-contained applications (J2EE application model), it does not enforce it. Workflow applications are installed in an HDFS directory. To submit a job for a workflow application the path to the HDFS directory where the application is must be specified. The layout of a workflow application directory is: - /workflow.xml - /config-default.xml | - /lib/ (*.jar;*.so) A workflow application must contain at least the workflow definition, the =workflow.xml= file. All configuration files and scripts (Pig and shell) needed by the workflow action nodes should be under the application HDFS directory. All the JAR files and native libraries within the application 'lib/' directory are automatically added to the map-reduce and pig jobs =classpath= and =LD_PATH=. Additional JAR files and native libraries not present in the application 'lib/' directory can be specified in map-reduce and pig actions with the 'file' element (refer to the map-reduce and pig documentation). The =config-default.xml= file defines, if any, default values for the workflow job parameters. This file must be in the Hadoop Configuration XML format. EL expressions are not supported and =user.name= property cannot be specified in this file. Any other resources like =job.xml= files referenced from a workflow action action node must be included under the corresponding path, relative paths always start from the root of the workflow application. ---++ 8 External Data Assumptions Oozie runs workflow jobs under the assumption all necessary data to execute an action is readily available at the time the workflow job is about to executed the action. In addition, it is assumed, but it is not the responsibility of Oozie, that all input data used by a workflow job is immutable for the duration of the workflow job. #JobLifecycle ---++ 9 Workflow Jobs Lifecycle A workflow job can have be in any of the following states: =PREP:= When a workflow job is first create it will be in =PREP= state. The workflow job is defined but it is not running. =RUNNING:= When a =CREATED= workflow job is started it goes into =RUNNING= state, it will remain in =RUNNING= state while it does not reach its end state, ends in error or it is suspended. =SUSPENDED:= A =RUNNING= workflow job can be suspended, it will remain in =SUSPENDED= state until the workflow job is resumed or it is killed. =SUCCEEDED:= When a =RUNNING= workflow job reaches the =end= node it ends reaching the =SUCCEEDED= final state. =KILLED:= When a =CREATED=, =RUNNING= or =SUSPENDED= workflow job is killed by an administrator or the owner via a request to Oozie the workflow job ends reaching the =KILLED= final state. =FAILED:= When a =RUNNING= workflow job fails due to an unexpected error it ends reaching the =FAILED= final state. *Workflow job state valid transitions:* * --> =PREP= * =PREP= --> =RUNNING= | =KILLED= * =RUNNING= --> =SUSPENDED= | =SUCCEEDED= | =KILLED= | =FAILED= * =SUSPENDED= --> =RUNNING= | =KILLED= #JobReRun ---++ 10 Workflow Jobs Recovery (re-run) Oozie must provide a mechanism by which a a failed workflow job can be resubmitted and executed starting after any action node that has completed its execution in the prior run. This is specially useful when the already executed action of a workflow job are too expensive to be re-executed. It is the responsibility of the user resubmitting the workflow job to do any necessary cleanup to ensure that the rerun will not fail due to not cleaned up data from the previous run. When starting a workflow job in recovery mode, the user must indicate what workflow nodes in the workflow should be skipped. The workflow nodes to skip must be specified in the =oozie.wf.rerun.skip.nodes= job configuration property, node names must be separated by commas. All workflow nodes indicated as skipped must have completed in the previous run. If a workflow node has not completed its execution in its previous run, and during the recovery submission is flagged as a node to be skipped, the recovery submission must fail. The recovery workflow job will run under the same workflow job ID as the original workflow job. To submit a recovery workflow job the target workflow job to recover must be in an end state (=SUCCEEDED=, =FAILED= or =KILLED=). A recovery run could be done using a new worklfow application path under certain constraints (see next paragraph). This is to allow users to do a one off patch for the workflow application without affecting other running jobs for the same application. A recovery run could be done using different workflow job parameters, the new values of the parameters will take effect only for the workflow nodes executed in the rerun. The workflow application use for a re-run must match the execution flow, node types, node names and node configuration for all executed nodes that will be skipped during recovery. This cannot be checked by Oozie, it is the responsibility of the user to ensure this is the case. Oozie provides the =int wf:run()= EL function to returns the current run for a job, this function allows workflow applications to perform custom logic at workflow definition level (i.e. in a =decision= node) or at action node level (i.e. by passing the value of the =wf:run()= function as a parameter to the task). #OozieWSAPI ---++ 11 Oozie Web Services API, V0 The Oozie Web Services API is a HTTP REST JSON API. All responses are in =UTF-8=. Assuming Oozie is runing at =OOZIE_URL=, the following web services end points are supported: * /versions * /v0/admin * /v0/job * /v0/jobs ---+++ 11.1 Versions End-Point This endpoint is for clients to perform protocol negotiation. It support only HTTP GET request and not sub-resources. It returns the supported Oozie protocol versions by the server. Current returned value is =0=. *Request:* GET /oozie/versions *Response:* HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 . [0] ---+++ 11.2 Admin End-Point This endpoint is for obtaining Oozie system status and configuration information. It supports the following sub-resources: =status, os-env, sys-props, configuration, instrumentation=. ---++++ 11.2.1 System Status A HTTP GET request returns the system status. *Request:* GET /oozie/v0/admin/status *Response:* HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 . {"safeMode":false} With a HTTP PUT request it is possible to bring in and out hte system from safemode. *Request:* PUT /oozie/v0/admin/status?safemode=true *Response:* HTTP/1.1 200 OK ---++++ 11.2.2 OS Environment A HTTP GET request returns the Oozie system OS environment. *Request:* GET /oozie/v0/admin/os-env *Response:* HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 . { TERM: "xterm", JAVA_HOME: "/usr/java/latest", XCURSOR_SIZE: "", SSH_CLIENT: "::ffff:127.0.0.1 49082 22", XCURSOR_THEME: "default", INPUTRC: "/etc/inputrc", HISTSIZE: "1000", PATH: "/usr/java/latest/bin" KDE_FULL_SESSION: "true", LANG: "en_US.UTF-8", ... } ---++++ 11.2.2 Java System Properties A HTTP GET request returns the Oozie Java system properties. *Request:* GET /oozie/v0/admin/java-sys-properties *Response:* HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 . { java.vm.version: "11.0-b15", sun.jnu.encoding: "UTF-8", java.vendor.url: "http://java.sun.com/", java.vm.info: "mixed mode", ... } ---++++ 11.2.2 Oozie Configuration A HTTP GET request returns the Oozie system configuration. *Request:* GET /oozie/v0/admin/configuration *Response:* HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 . { oozie.service.SchedulerService.threads: "5", oozie.service.ActionService.executor.classes: " org.apache.oozie.wf.action.decision.DecisionActionExecutor, org.apache.oozie.wf.action.hadoop.HadoopActionExecutor, org.apache.oozie.wf.action.hadoop.FsActionExecutor ", oozie.service.CallableQueueService.threads.min: "10", oozie.service.DBLiteWorkflowStoreService.oozie.autoinstall: "true", ... } ---++++ 11.2.3 Oozie Instrumentation A HTTP GET request returns the Oozie instrumentation information. *Request:* GET /oozie/v0/admin/instrumentation *Response:* HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 . { timers: [ { group: "db", data: [ { ownMinTime: 2, ownTimeStdDev: 0, totalTimeStdDev: 0, ownTimeAvg: 3, ticks: 117, name: "update-workflow", ownMaxTime: 32, totalMinTime: 2, totalMaxTime: 32, totalTimeAvg: 3 }, ... ] }, ... ], samplers: [ { group: "callablequeue", data: [ { name: "threads.active", value: 1.8333333333333333 }, { name: "delayed.queue.size", value: 0 }, { name: "queue.size", value: 0 } ] }, ... ], variables: [ { group: "jvm", data: [ { name: "max.memory", value: 506920960 }, { name: "total.memory", value: 56492032 }, { name: "free.memory", value: 45776800 } ] }, ... ] } ---++++ 11.2.4 Version A HTTP GET request returns the Oozie build version. *Request:* GET /oozie/v0/admin/build-version *Response:* HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 . {buildVersion: "0.18.3.o0.1" } ---+++ 11.3 Job and Jobs End-Points These endpoints is for submitting, managing and retrieving information of jobs. ---++++ 11.3.1 Job Submission A HTTP POST request with an XML configuration as payload creates a job. *Request:* POST /oozie/v0/jobs Content-Type: application/xml;charset=UTF-8 . user.name tucu oozie.wf.application.path hdfs://foo:9000/user/tucu/myapp/ ... *Response:* HTTP/1.1 201 CREATED Content-Type: application/json;charset=UTF-8 . { id: "job-3" } The created job is in PREP status. If the query string parameter 'action=start' is provided in the POST URL, the job will be started immediatly and its status will be RUNNING. ---++++ 11.3.1 Managing the Job A HTTP PUT request starts, suspends, resumes or kills a job. *Request:* PUT /oozie/v0/job/job-3?action=start *Response:* HTTP/1.1 200 OK Valid values for the 'action' parameter are 'start', 'suspend', 'resume' and 'kill'. ---++++ 11.3.1 Job Information A HTTP GET request retrieves the job information. *Request:* GET /oozie/v0/job/job-3?show=info *Response:* HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 . { id: "0-200905191240-oozie-tucu", appName: "indexer-workflow", appPath: "hdfs://user/tucu/indexer.wf", externalId: "0-200905191230-oozie-pepe", user: "tucu", group: "other", status: "RUNNING", conf: " ... ", createdTime: "Thu, 01 Jan 2009 00:00:00 GMT", startTime: "Fri, 02 Jan 2009 00:00:00 GMT", endTime: null, run: 0, actions: [ { id: "0-200905191240-oozie-tucu@indexer", name: "indexer", type: "map-reduce", conf: " ...", startTime: "Thu, 01 Jan 2009 00:00:00 GMT", endTime: "Fri, 02 Jan 2009 00:00:00 GMT", status: "OK", externalId: "job-123-200903101010", externalStatus: "SUCCEEDED", trackerUri: "foo:9001", consoleUrl: "http://foo:50040/jobdetailshistory.jsp?jobId=...", transition: "reporter", data: null, errorCode: null, errorMessage: null, retries: 0 }, ... ] } ---++++ 11.3.2 Job Definition A HTTP GET request retrieves the workflow job definition file. *Request:* GET /oozie/v0/job/job-3?show=definition *Response:* HTTP/1.1 200 OK Content-Type: application/xml;charset=UTF-8 . ... ---++++ 11.3.3 Job Log A HTTP GET request retrieves the job log. *Request:* GET /oozie/v0/job/job-3?show=log *Response:* HTTP/1.1 200 OK Content-Type: text/plain;charset=UTF-8 . ... 23:21:31,272 TRACE oozieapp:526 - USER[tucu] GROUP[other] TOKEN[-] APP[test-wf] JOB[0-20090518232130-oozie-tucu] ACTION[mr-1] Start 23:21:31,305 TRACE oozieapp:526 - USER[tucu] GROUP[other] TOKEN[-] APP[test-wf] JOB[0-20090518232130-oozie-tucu] ACTION[mr-1] End ... ---++++ 11.3.4 Jobs Information A HTTP GET request retrieves the jobs information. *Request:* GET /oozie/v0/jobs?filter=user%3Dtucu&offset=1&len=50 Note that the filter is URL encoded, its decoded value is user=tucu. *Response:* HTTP/1.1 200 OK Content-Type: application/json;charset=UTF-8 . { offset: 1, len: 50, total: 1002, workflows: [ { id: "0-200905191240-oozie-tucu", appName: "indexer-workflow", appPath: "hdfs://user/tucu/indexer-wf", user: "tucu", group: "other", status: "RUNNING", conf: " ... ", createdTime: "Thu, 01 Jan 2009 00:00:00 GMT", startTime: "Fri, 02 Jan 2009 00:00:00 GMT", endTime: null, run: 0, actions: [ ] }, ... ] } No action information is returned when querying for multiple jobs. The syntax for the filter is [NAME=VALUE][;NAME=VALUE]* Valid filter names are: * name: the workflow application name from the workflow definition * user: the user that submitted the job * group: the group for the job * status: the status of the job The query will do an AND among all the filter names. The query will do an OR among all the filter values for the same name. Multiple values must be specified as different name value pairs. Additionaly the =start= and =len= parameters can be used for pagination. The start parameter is base 1. ---++ 12 Client API Oozie provides a Java [[./apidocs/org/apache/oozie/client/package-summary.html][Client API]] that allows to perform all common workflow job operations. The client API includes a [[./apidocs/org/apache/oozie/client/LocalOozie.html][LocalOozie class]] useful for testing a workflow from within an IDE and for unit testing purposes. The Client API is implemented as a client of the Web Services API. ---++ 13 Command Line Tools Oozie provides command line tool that allows to perform all common workflow job operations. The command line tool is implemented as a client of the Web Services API. ---++ 14 Web UI Console Oozie provides a read-only Web based console that allows to allow to monitor Oozie system status, workflow applications status and workflow jobs status. The Web base console is implemented as a client of the Web Services API. ---++ 15 Customizing Oozie with Extensions Out of the box Oozie provides support for a predefined set of action node types and Expression Language functions. Oozie provides a well defined API, [[./apidocs/org/apache/oozie/dag/action/package-summary.html][Action executor]] API, to add support for additional action node types. Extending Oozie should not require any code change to the Oozie codebase. It will require adding the JAR files providing the new functionality and declaring them in Oozie system configuration. ---++ 16 Workflow Jobs Priority Oozie does not handle workflow jobs priority. As soon as a workflow job is ready to do a transition, Oozie will trigger the transition. Workflow transitions and action triggering are assumed to be fast and lightweight operations. Oozie assumes that the remote systems are properly sized to handle the amount of remote jobs Oozie will trigger. Any prioritization of jobs in the remote systems is outside of the scope of Oozie. Workflow applications can influence the remote systems priority via configuration if the remote systems support it. ---++ Appendixes #OozieWFSchema ---+++ Appendix A, Oozie XML-Schema ---++++ Oozie Schema Version 0.2 ---++++ Oozie SLA Version 0.1 * *Oozie SLA schema is supported in Oozie schema version 0.2* ---++++ Oozie Schema Version 0.1 #OozieWFExamples ---+++ Appendix B, Workflow Examples ---++++!! Fork and Join Example The following workflow definition example executes 4 Map-Reduce jobs in 3 steps, 1 job, 2 jobs in parallel and 1 job. The output of the jobs in the previous step are use as input for the next jobs. *Required workflow job parameters:* * =jobtracker= : JobTracker HOST:PORT * =namenode= : NameNode HOST:PORT * =input= : input directory * =output= : output directory ${jobtracker} ${namenode} mapred.mapper.class org.apache.hadoop.example.IdMapper mapred.reducer.class org.apache.hadoop.example.IdReducer mapred.map.tasks 1 mapred.input.dir ${input} mapred.output.dir /usr/foo/${wf:id()}/temp1 ${jobtracker} ${namenode} mapred.mapper.class org.apache.hadoop.example.IdMapper mapred.reducer.class org.apache.hadoop.example.IdReducer mapred.map.tasks 1 mapred.input.dir /usr/foo/${wf:id()}/temp1 mapred.output.dir /usr/foo/${wf:id()}/temp2 ${jobtracker} ${namenode} mapred.mapper.class org.apache.hadoop.example.IdMapper mapred.reducer.class org.apache.hadoop.example.IdReducer mapred.map.tasks 1 mapred.input.dir /usr/foo/${wf:id()}/temp1 mapred.output.dir /usr/foo/${wf:id()}/temp3 ${jobtracker} ${namenode} mapred.mapper.class org.apache.hadoop.example.IdMapper mapred.reducer.class org.apache.hadoop.example.IdReducer mapred.map.tasks 1 mapred.input.dir /usr/foo/${wf:id()}/temp2,/usr/foo/${wf:id()}/temp3 mapred.output.dir ${output} Map/Reduce failed, error message[${wf:errorMessage()}] [[index][::Go back to Oozie Documentation Index::]]