I am a bit confused about place of tasktracker in Hadoop-2.x.
Daemons in Hadoop-1.x are namenode, datanode, jobtracker, taskracker and secondaryna
Task tracker has been split into three components in Hadoop YARN architecture : Resource Manager, Application Manager and Application Master.
The fundamental idea of YARN is to split up the functionalities of resource management and job scheduling/monitoring into separate daemons. The idea is to have a global ResourceManager (RM) and per-application ApplicationMaster (AM). An application is either a single job or a DAG of jobs.
The ResourceManager has two main components: Scheduler and ApplicationsManager.
The Scheduler
is responsible for allocating resources to the various running applications subject to familiar constraints of capacities, queues etc. The Scheduler is pure scheduler in the sense that it performs no monitoring or tracking of status for the application.
The ApplicationsManager
is responsible for accepting job-submissions, negotiating the first container for executing the application specific ApplicationMaster and provides the service for restarting the ApplicationMaster container on failure.
The per-application ApplicationMaster
has the responsibility of negotiating appropriate resource containers from the Scheduler, tracking their status and monitoring for progress.
Have a look at documentation link
Have a look at this SE question for more details.
What additional benefit does Yarn bring to the existing map reduce?