What is Job Tracker role in Hadoop?

Question

A mapreduce job can be run as jar file from terminal or directly from eclipse IDE. When a job run as jar file from terminal it uses multiple jvm and all resources of cluster. Does the same thing happen when we run from IDE. I have run a job on both and it takes less time on IDE than jar file on terminal.

Answer 1

The JobTracker is the service within Hadoop that farms out MapReduce tasks to specific nodes in the cluster, ideally the nodes that have the data, or at least are in the same rack.

1: Client applications submit jobs to the Job tracker.
2: The JobTracker talks to the NameNode to determine the location of the data
3: The JobTracker locates TaskTracker nodes with available slots at or near the data
4: The JobTracker submits the work to the chosen TaskTracker nodes.
5: The TaskTracker nodes are monitored. If they do not submit heartbeat signals often enough, they are deemed to have failed and 6: the work is scheduled on a different TaskTracker.
A TaskTracker will notify the JobTracker when a task fails. The JobTracker decides what to do then: it may resubmit the job
elsewhere, it may mark that specific record as something to avoid, and it may may even blacklist the TaskTracker as unreliable.
7: When the work is completed, the JobTracker updates its status.
8: Client applications can poll the JobTracker for information.
The JobTracker is a point of failure for the Hadoop MapReduce service. If it goes down, all running jobs are halted.