How to chain multiple MapReduce jobs in Hadoop

When running MapReduce jobs it is possible to have several MapReduce steps with overall job scenarios means the last reduce output will be used as input for the next map job.

Map1 -> Reduce1 -> Map2 -> Reduce2 -> Map3...

While searching for an answer to my MapReduce job, I stumbled upon several cool new ways to achieve my objective. Here are some of the ways:


Using Map/Reduce JobClient.runJob() Library to chain jobs:

You can easily chain jobs together in this fashion by writing multiple driver methods, one for each job. Call the first driver method, which uses JobClient.runJob() to run the job and wait for it to complete. When that job has completed, then call the next driver method, which creates a new JobConf object referring to different instances of Mapper and Reducer, etc. The first job in the chain should write its output to a path which is then used as the input path for the second job. This process can be repeated for as many jobs are necessary to arrive at a complete solution to the problem


Method 1:

  • First create the JobConf object "job1" for the first job and set all the parameters with "input" as inputdirectory and "temp" as output directory. Execute this job:
  • Immediately below it, create the JobConf object "job2" for the second job and set all the parameters with "temp" as inputdirectory and "output" as output directory. Finally execute second job:


Method 2:

  • Create two JobConf objects and set all the parameters in them just like (1) except that you don't use
  • Then create two Job objects with jobconfs as parameters: Job job1=new Job(jobconf1); Job job2=new Job(jobconf2);
  • Using the jobControl object, you specify the job dependencies and then run the jobs: JobControl jbcntrl=new JobControl("jbcntrl"); jbcntrl.addJob(job1); jbcntrl.addJob(job2); job2.addDependingJob(job1);;


Using Oozie which is Hadoop Workflow Service described as below:

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. fork and join nodes must be used in pairs. The join node assumes concurrent execution paths are children of the same fork node.


The name attribute in the fork node is the name of the workflow fork node. The to attribute in the transition elements in the fork node indicate the name of the workflow node that will be part of the concurrent execution. The name attribute in the join node is the name of the workflow join node. The to attribute in the transition element in the join node indicates the name of the workflow node that will executed after all  3.1.5 Fork and Join Control Nodes 5concurrent execution paths of the corresponding fork arrive to the join node.



<hadoop−workflow name="sample−wf">


    <fork name="forking">

        <transition to="firstparalleljob"/>

        <transition to="secondparalleljob"/>


    <hadoop name="firstparalleljob">


       <transition name="OK" to="joining"/>

       <transition name="ERROR" to="fail"/>


    <hadoop name="secondparalleljob">


        <transition name="OK" to="joining"/>

        <transition name="ERROR" to="fail"/>


    <join name="joining">

        <transition to="nextaction"/>





Using Cascading Library (GPL):

Cascading is a Data Processing API, Process Planner, and Process Scheduler used for defining and executing complex, scale-free, and fault tolerant data processing workflows on an Apache Hadoop cluster. All without having to 'think' inMapReduce.


Using Apache Mahout Recommender Job Sample:

Apache Mahout project has a sample call which chains together multiple MapReduce jobs. You can find the sample here:


Using a simple java library name “Hadoop-orchestration” at GitHub:

This library, enables execution of multiple Hadoop jobs as a workflow. The job configuration and workflow defining inter job dependency is configured in a JSON file. Everything is externally configurable and does not require any change in existing map reduce implementation to be part of a workflow. Details can be found here. Source code and jar is available in github.


Comments (3)

  1. Shashank says:

    I see many people using referencing your post. New version of API does not use jobconf object, what is the way to do chaining for new API

  2. vignesh says:

    hai thank for your reviews.

    <a href="">Hadoop Training in Chennai</a>

  3. vignesh says:

    Hai thanks a lot.

    <a href="">Hadoop Training in Chennai</a>

Skip to main content