In the task scheduling of YARN. Once the Application Master applies for resources, it communicates with the corresponding Resource Manager and asks it to start the task

Question

Options

• ATrue
• BFalse

• A
  24% (15)
• B
  76% (48)

Explanation

Option B is correct because after the Application Master (AM) receives resource allocations from the ResourceManager, it communicates directly with the NodeManagers - not the ResourceManager - to launch and start the actual tasks. The ResourceManager's role ends at resource negotiation and allocation; it does not handle task execution. The NodeManagers are responsible for managing containers and starting tasks on their respective nodes, which is a deliberate separation of concerns in YARN's architecture.

Option A is wrong because it conflates two distinct YARN components: the ResourceManager (cluster-level resource scheduler) and the NodeManager (node-level task executor). The AM only talks back to the ResourceManager for resource requests and heartbeats, not to initiate task startup.

Memory tip: Think of YARN as a hiring agency model - the ResourceManager is the agency that matches jobs to workers (allocates resources), while NodeManagers are the on-site managers who actually put workers to their tasks. The Application Master goes through the agency to find workers, then directly contacts the on-site manager to start the work.

No community discussion yet for this question.