MapReduce V2 (MRv2/YARN) splits which two major functions of the jobtracker into separate daemons?

The correct answer is E. Job scheduling/monitoring F. Resource management. MapReduce has undergone a complete overhaul and CDH4 now includes MapReduce 2.0 (MRv2). The fundamental idea of MRv2's YARN architecture is to split up the two primary responsibilities of the JobTracker -- resource management (F) and job scheduling/monitoring (E) - - into…

Resource Management

Question

Options

AManaging tasks
BManaging file system metadata
CLaunching tasks
DJob coordination between the resource manager and the node manager
EJob scheduling/monitoring
FResource management
GHealth status check (heartbeats)
HMapReduce metric reporting

How the community answered

(68 responses)

A
3% (2)
B
1% (1)
C
13% (9)
D
1% (1)
E
75% (51)
G
6% (4)

Explanation

MapReduce has undergone a complete overhaul and CDH4 now includes MapReduce 2.0 (MRv2). The fundamental idea of MRv2's YARN architecture is to split up the two primary responsibilities of the JobTracker -- resource management (F) and job scheduling/monitoring (E) - - into separate daemons: a global ResourceManager (RM) and per- application ApplicationMasters (AM). With MRv2, the ResourceManager (RM) and per-node NodeManagers (NM), form the data-computation framework. The ResourceManager service effectively replaces the functions of the JobTracker, and NodeManagers run on slave nodes instead of TaskTracker daemons. The per-application ApplicationMaster is, in effect, a framework specific library and is tasked with negotiating resources from the ResourceManager and working with the NodeManager(s) to execute and monitor the tasks.

Topics

#YARN#JobTracker#ResourceManager#job scheduling

Community Discussion

No community discussion yet for this question.

Full CCA-410 Practice