Book Image

Apache Oozie Essentials

By : Jagat Singh
Book Image

Apache Oozie Essentials

By: Jagat Singh

Overview of this book

As more and more organizations are discovering the use of big data analytics, interest in platforms that provide storage, computation, and analytic capabilities is booming exponentially. This calls for data management. Hadoop caters to this need. Oozie fulfils this necessity for a scheduler for a Hadoop job by acting as a cron to better analyze data. Apache Oozie Essentials starts off with the basics right from installing and configuring Oozie from source code on your Hadoop cluster to managing your complex clusters. You will learn how to create data ingestion and machine learning workflows. This book is sprinkled with the examples and exercises to help you take your big data learning to the next level. You will discover how to write workflows to run your MapReduce, Pig ,Hive, and Sqoop scripts and schedule them to run at a specific time or for a specific business requirement using a coordinator. This book has engaging real-life exercises and examples to get you in the thick of things. Lastly, you’ll get a grip of how to embed Spark jobs, which can be used to run your machine learning models on Hadoop. By the end of the book, you will have a good knowledge of Apache Oozie. You will be capable of using Oozie to handle large Hadoop workflows and even improve the availability of your Hadoop environment.
Table of Contents (16 chapters)
Apache Oozie Essentials
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Coordinator controls


The execution policies for the actions of a Coordinator job can be defined in the Coordinator application. There are different types of Coordinator controls, as shown in the following figure:

Coordinator controls

Here's a brief explanation of the Coordinator controls present in the preceding figure:

  • timeout: The timeout control allows us to say how long the Coordinator action will be in the waiting or ready state before timing out on its execution, for example, five minutes.

  • concurrency: Using this control, we can specify the concurrency for the Coordinator actions. It specifies how many Coordinator actions are allowed to run concurrently (the running status).

  • execution: If there is a backlog of Coordinators, this control helps to decide which one should be executed. The different choices are oldest first (FIFO), newest first (LIFO), none (NONE), and last one only (LAST_ONLY).

  • throttle: The throttle control specifies the maximum number of Coordinator actions that are allowed...