Azkaban

Oozie

Scheduling a job HTTP POST request from command line It has a feature called ‘coordinators’. A coordinator is an XML file that have the description of workflows it consumes.
Also provides a UI for scheduling jobs with cron precision. It also schedules the workflow accordingly and before running confirms that required datasets are available and then runs.
No concept of ‘coordinators’ Has a concept of “startDate”
Security Hadoop jobs run under a single account Built in support for secure hadoop including kerberos. Hadoop is configured with proxy allowing oozie to to run run jobs as that user.
Azkaban works with Hadoop security via the hadoopsecuritymanager. So, Hadoop security is not really on Azkaban, but on Hadoop itself.
Property Management Global properties embedded with azkaban.

Global properties can be configured for different running environments (testing, staging, production).

No notion of global properties. each run or workflow has set of properties and need to be specified with the job itself.
Can specify number of max reducers
No need to redeploy after changing the global properties.

pic courtesy: devianart.com

Azkaban

Oozie

Scheduling a job HTTP POST request from command line It has a feature called ‘coordinators’. A coordinator is an XML file that have the description of workflows it consumes.
Also provides a UI for scheduling jobs with cron precision. It also schedules the workflow accordingly and before running confirms that required datasets are available and then runs.
No concept of ‘coordinators’ Has a concept of “startDate”
Security Hadoop jobs run under a single account Built in support for secure hadoop including kerberos. Hadoop is configured with proxy allowing oozie to to run run jobs as that user.
Azkaban works with Hadoop security via the hadoopsecuritymanager. So, Hadoop security is not really on Azkaban, but on Hadoop itself.
Property Management Global properties embedded with azkaban.
Global properties can be configured for different running environments (testing, staging, production).
No notion of global properties. each run or workflow has set of properties and need to be specified with the job itself.
Can specify number of max reducers
No need to redeploy after changing the global properties.

Pic Courtesy: devianart.com