Scheduling and Workflow - Big Data Made Easy: A Working Guide to the Complete Hadoop Toolset - page 146

The left column of Figure 5-5 gives a list of job IDs that are issued when each Oozie job is submitted. The next
column to the right shows the workflow name—in this case, FuelWorkFlow. The Status column shows the job's
last status, which could be Prep, Running, Suspended, Succeeded, Failed, or Killed. Table 5-1 lists the meanings of
these statuses.

Table 5-1. Job Statuses and Meanings

Status Meaning

PREP

Job just created; it can be moved to Running or Killed.

RUNNING

Job is being executed; its state can change to Suspended, Succeeded, Killed, or Failed.

SUSPENDED

A running job can be suspended; its state can change to Running or Killed.

SUCCEEDED

The job sucessfully reached its end state.

FAILED

The job encountered an unexpected error.

KILLED

A job action failed or the job was killed by an administrator.

The User and date columns show which Linux user account ran the job and when it was created, started, and
modified. The tabs at the top of the display are for workflows, coordinator jobs, and bundling. Coordinator jobs are
for scheduling, either via time or event, while bundling allows the grouping of coordinator jobs. The other tabs are for
configuration information and metrics.
By selecting an individual workflow job, you can bring up a job-related Oozie window. In Figure 5-6 , I have
selected the topmost successful job on the list. As you can see, the Job Info tab shows the job's attributes and
its actions and status details. The Job Definition tab contains the xml contents of the workflow, while the Job
Configuration tab shows configured attributes for the job. The Job Log tab shows the logged output for this job, as
Figure 5-7 shows.