Memory and container sizing in Hadoop - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a container in Hadoop YARN?

A container is a resource allocation unit in Hadoop YARN that bundles CPU, memory, and other resources to run a task.

beginner

Why is memory sizing important for containers in Hadoop?

Proper memory sizing ensures tasks run efficiently without crashing or wasting resources, balancing performance and cluster utilization.

intermediate

What happens if a container is assigned less memory than needed?

The container may fail or the task may crash due to out-of-memory errors, causing job failures or retries.

intermediate

How does YARN decide container size?

YARN uses configuration settings like yarn.scheduler.minimum-allocation-mb and yarn.scheduler.maximum-allocation-mb to control container sizes.

intermediate

What is the impact of setting container memory too high?

It can lead to inefficient resource use, fewer containers running simultaneously, and lower cluster throughput.

What does a container in Hadoop YARN include?

A CPU and memory resources

B Only CPU resources

C Only memory resources

D Disk space only

Containers bundle CPU, memory, and sometimes other resources to run tasks.

Which configuration controls the minimum container memory in YARN?

A yarn.nodemanager.resource.memory-mb

B yarn.scheduler.minimum-allocation-mb

C mapreduce.task.io.sort.mb

D yarn.resourcemanager.scheduler.class

yarn.scheduler.minimum-allocation-mb sets the smallest container size allowed.

What is a risk of assigning too little memory to a container?

A Running too many containers

B Wasting cluster resources

C Task failure due to out-of-memory

D Improved performance

Insufficient memory causes tasks to crash or fail.

If container memory is set too high, what happens?

A No effect on cluster

B More containers run at once

C Tasks run faster always

D Fewer containers run at once

High memory per container reduces how many containers fit on nodes.

Which is NOT a resource managed by YARN containers?

A Network bandwidth

B Memory

C CPU

D Disk space

YARN containers manage CPU, memory, and disk but not network bandwidth directly.

Explain why correct memory and container sizing is important in Hadoop YARN.

Think about what happens if memory is too low or too high.

Describe how YARN uses configuration to control container sizes.

Focus on yarn.scheduler.minimum-allocation-mb and yarn.scheduler.maximum-allocation-mb.

Practice

1. What is the main purpose of setting container memory size in Hadoop?

easy

A. To set the network bandwidth for data transfer

B. To increase the disk space available for Hadoop jobs

C. To control the number of CPU cores assigned to a task

D. To limit the amount of memory a task can use during execution

Solution

1. Step 1: Understand container memory role and compare options

   Container memory size limits how much RAM a Hadoop task can use while running. Only To limit the amount of memory a task can use during execution correctly describes this purpose; others relate to disk, CPU, or network, which are unrelated.

2. Final Answer:

   To limit the amount of memory a task can use during execution -> Option D

3. Quick Check:

   Container memory = task RAM limit [OK]

Hint: Container memory controls RAM usage per task [OK]

Common Mistakes:

• Confusing memory with disk space
• Thinking container memory controls CPU cores
• Assuming it sets network bandwidth

2. Which of the following is the correct way to set the Java heap size for a Hadoop container in the configuration?

easy

A. mapreduce.map.memory.mb=512\nmapreduce.map.java.opts=-Xmx5120m

B. mapreduce.map.memory.mb=2048\nmapreduce.map.java.opts=-Xmx1536m

C. mapreduce.map.memory.mb=1024\nmapreduce.map.java.opts=-Xmx2048m

D. mapreduce.map.memory.mb=4096\nmapreduce.map.java.opts=-Xmx8192m

Solution

1. Step 1: Understand heap size vs container memory and check options

   Java heap size (-Xmx) must be less than container memory to avoid errors. mapreduce.map.memory.mb=2048\nmapreduce.map.java.opts=-Xmx1536m sets container memory to 2048 MB and heap to 1536 MB, which is valid. Others have heap larger than container memory, causing errors.

2. Final Answer:

   mapreduce.map.memory.mb=2048\nmapreduce.map.java.opts=-Xmx1536m -> Option B

3. Quick Check:

   Heap size < container memory [OK]

Hint: Heap size must be smaller than container memory [OK]

Common Mistakes:

• Setting heap size larger than container memory
• Using inconsistent units (MB vs GB)
• Forgetting to set Java opts after memory

3. Given the following configuration:

mapreduce.reduce.memory.mb=4096
mapreduce.reduce.java.opts=-Xmx3072m

What will happen if a reduce task tries to use 3500 MB heap memory?

medium

A. The task will run successfully using 3500 MB heap

B. The task will automatically increase container memory

C. The task will fail due to exceeding Java heap size limit

D. The task will fail due to exceeding container memory limit

Solution

1. Step 1: Compare requested heap with limits

   Heap limit is 3072 MB, but task tries 3500 MB, which exceeds Java heap limit (-Xmx). Container memory is 4096 MB, so 3500 MB fits container but exceeds heap limit, causing failure.

2. Final Answer:

   The task will fail due to exceeding Java heap size limit -> Option C

3. Quick Check:

   Heap > Java heap limit = failure [OK]

Hint: Heap usage must not exceed Java heap size (-Xmx) [OK]

Common Mistakes:

• Confusing container memory with Java heap size
• Assuming container memory limits heap directly
• Thinking container memory auto-adjusts

4. Identify the error in this Hadoop container memory configuration:

mapreduce.map.memory.mb=1024
mapreduce.map.java.opts=-Xmx1536m

medium

A. Java heap size is larger than container memory size

B. Container memory size is too large for the job

C. Java opts syntax is incorrect

D. No error, configuration is valid

Solution

1. Step 1: Compare Java heap size and container memory

   Heap size (-Xmx1536m) is 1536 MB, which is larger than container memory (1024 MB). This causes the task to fail because heap cannot exceed container memory.

2. Final Answer:

   Java heap size is larger than container memory size -> Option A

3. Quick Check:

   Heap > container memory = error [OK]

Hint: Heap size must never exceed container memory [OK]

Common Mistakes:

• Ignoring heap size limits
• Assuming syntax error instead of sizing error
• Thinking container memory can auto-expand

5. You have a Hadoop job with 10 map tasks. Each map task requires 3 GB of Java heap memory. To avoid container failures, what is the minimum container memory size you should set per map task?

hard

A. 4 GB

B. 3 GB

C. 6 GB

D. 10 GB

Solution

1. Step 1: Calculate container memory with overhead

   Container memory must be larger than Java heap size to allow overhead (usually 25-30%). Heap = 3 GB, so container memory should be at least 3 GB + 25% = 3.75 GB, rounded to 4 GB.

2. Final Answer:

   4 GB -> Option A

3. Quick Check:

   Container memory > heap size + overhead [OK]

Hint: Add 25% overhead to heap for container memory [OK]

Common Mistakes:

• Setting container memory equal to heap size
• Ignoring overhead memory needs
• Confusing total job memory with per-task memory