CCA-500 · Question #27
You are migrating a cluster from MApReduce version 1 (MRv1) to MapReduce version 2 (MRv2) on YARN. You want to maintain your MRv1 TaskTracker slot capacities when you migrate. What should you do/
The correct answer is D. Configure yarn.nodemanager.resource.memory-mb and yarn.nodemanager.resource.cpu- vcores. In MRv1, the mapred.tasktracker.map.tasks.maximum and mapred.tasktracker.reduce.tasks.maximum properties dictated how many map and reduce slots each TaskTracker had. These properties no longer exist in YARN. Instead, YARN uses yarn.nodemanager.resource.memory-mb and…
Question
You are migrating a cluster from MApReduce version 1 (MRv1) to MapReduce version 2 (MRv2) on YARN. You want to maintain your MRv1 TaskTracker slot capacities when you migrate. What should you do/
Options
- AConfigure yarn.applicationmaster.resource.memory-mb and yarn.applicationmaster.resource.cpu-
- BYou don't need to configure or balance these properties in YARN as YARN dynamically balances
- CConfigure mapred.tasktracker.map.tasks.maximum and
- DConfigure yarn.nodemanager.resource.memory-mb and yarn.nodemanager.resource.cpu- vcores
How the community answered
(23 responses)- A4% (1)
- B13% (3)
- C4% (1)
- D78% (18)
Explanation
In MRv1, the mapred.tasktracker.map.tasks.maximum and mapred.tasktracker.reduce.tasks.maximum properties dictated how many map and reduce slots each TaskTracker had. These properties no longer exist in YARN. Instead, YARN uses yarn.nodemanager.resource.memory-mb and yarn.nodemanager.resource.cpu-vcores, which control the amount of memory and CPU on each host, both available to both maps and reduces. e_to_yarn_migrate.html#concept_e4c_3my_xl_unique_1
Topics
Community Discussion
No community discussion yet for this question.