Memory management and garbage collection in Apache Spark - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Spark's Memory Management

In Apache Spark, what is the primary purpose of the Unified Memory Manager?

A To manage only the storage memory for caching RDDs

B To divide memory strictly between execution and storage without sharing

C To allow dynamic sharing of memory between execution and storage tasks

D To allocate memory only for shuffle operations

💡 Hint

Think about how Spark balances memory needs for computation and caching.

The Unified Memory Manager in Spark dynamically shares memory between execution (for tasks like shuffle, join) and storage (for caching data), improving resource utilization.

❓ query_result

intermediate

Effect of Garbage Collection on Spark Job Performance

Consider a Spark job with frequent full garbage collections (GC). What is the most likely impact on the job's performance?

A No impact on performance

B Degraded performance due to GC pauses

C Improved performance due to memory cleanup

D Faster task execution because of less memory usage

💡 Hint

Think about what happens when the JVM pauses for garbage collection.

Frequent full GC causes JVM pauses, which delay task execution and degrade overall Spark job performance.

📝 Syntax

advanced

Configuring Spark Memory Fraction

Which Spark configuration setting controls the fraction of JVM heap used for execution and storage memory?

A spark.memory.fraction

B spark.memory.storageFraction

C spark.executor.memory

D spark.shuffle.memoryFraction

💡 Hint

Look for the setting that defines the overall memory fraction for unified memory.

spark.memory.fraction sets the fraction of JVM heap used for both execution and storage memory in Spark's unified memory management.

🔧 Debug

advanced

Diagnosing Memory Leak in Spark Application

A Spark application is running out of memory despite having sufficient executor memory configured. Which of the following is the most likely cause?

A RDDs are not being unpersisted after use

B Executor cores are set too high

C Using broadcast variables correctly

D Too many shuffle partitions configured

💡 Hint

Think about what happens if cached data is never released.

If RDDs are cached but not unpersisted when no longer needed, they consume memory unnecessarily, causing memory leaks.

❓ optimization

expert

Optimizing Garbage Collection for Large Spark Jobs

Which JVM garbage collector is generally recommended for large Spark jobs to reduce GC pause times?

A Serial Garbage Collector

B Parallel Garbage Collector

C CMS Garbage Collector

D G1 Garbage Collector

💡 Hint

Consider a collector designed for low pause times and large heaps.

The G1 Garbage Collector is designed for large heaps and aims to reduce pause times, making it suitable for large Spark jobs.

Practice

1. What is the main purpose of garbage collection in Apache Spark?

easy

A. To increase the size of the memory available to Spark

B. To automatically free up memory by removing unused objects

C. To manually allocate memory for Spark tasks

D. To store data permanently on disk

Solution

1. Step 1: Understand garbage collection role

   Garbage collection automatically removes objects that are no longer needed to free memory.

2. Step 2: Identify purpose in Spark context

   This helps Spark avoid running out of memory and keeps it running smoothly.

3. Final Answer:

   To automatically free up memory by removing unused objects -> Option B

4. Quick Check:

   Garbage collection = frees unused memory [OK]

Hint: Garbage collection cleans unused data automatically [OK]

Common Mistakes:

• Thinking garbage collection increases memory size
• Confusing manual memory allocation with garbage collection
• Believing garbage collection stores data permanently

2. Which of the following is the correct way to set the executor memory in Spark configuration?

easy

A. spark.executor.memory: 4g

B. spark.executor.memory = 4g

C. set spark.executor.memory to 4g

D. spark.executor.memory 4g

Solution

1. Step 1: Recall Spark config syntax

   Spark configuration in spark-defaults.conf uses "key value" format with space separator, no equals sign.

2. Step 2: Check each option

   A: "spark.executor.memory 4g" matches exactly. B has = incorrect for conf file. C and D invalid syntax.

3. Final Answer:

   spark.executor.memory 4g -> Option D

4. Quick Check:

   Config syntax = key value [OK]

Hint: Spark configs use key value format with space [OK]

Common Mistakes:

• Using '=' sign instead of space separator
• Writing config as a sentence
• Using colon instead of space

3. Given the Spark code snippet below, what will happen if the executor memory is too small?

val spark = SparkSession.builder().appName("Test").getOrCreate()
spark.conf.set("spark.executor.memory", "512m")
val data = spark.range(100000000).cache()
data.count()

medium

A. The job may fail with an OutOfMemoryError during execution

B. The job will store data only on disk without caching

C. The job will ignore the memory setting and use default

D. The job will run faster because less memory is used

Solution

1. Step 1: Understand executor memory effect

   Setting executor memory too low limits how much data Spark can hold in memory.

2. Step 2: Analyze caching and large data

   Caching large data with small memory causes Spark to run out of memory and throw errors.

3. Final Answer:

   The job may fail with an OutOfMemoryError during execution -> Option A

4. Quick Check:

   Small memory + caching large data = failure [OK]

Hint: Small executor memory + caching large data causes failure [OK]

Common Mistakes:

• Assuming job runs faster with less memory
• Thinking Spark ignores memory settings
• Believing caching always stores data on disk

4. You see frequent garbage collection pauses slowing down your Spark job. Which change can help reduce these pauses?

medium

A. Disable caching of data

B. Decrease the number of Spark partitions

C. Increase executor memory size

D. Set spark.executor.memory to zero

Solution

1. Step 1: Identify cause of GC pauses

   Frequent garbage collection happens when memory is too small to hold data efficiently.

2. Step 2: Choose solution to reduce GC pauses

   Increasing executor memory gives more space, reducing how often GC runs.

3. Final Answer:

   Increase executor memory size -> Option C

4. Quick Check:

   More memory = fewer GC pauses [OK]

Hint: More memory reduces garbage collection frequency [OK]

Common Mistakes:

• Setting memory to zero causes job failure
• Decreasing partitions may not reduce GC pauses
• Disabling caching may not fix GC issues

5. You want to optimize a Spark job that processes large datasets and experiences frequent garbage collection. Which combination of settings is best to improve performance?

hard

A. Increase executor memory and enable Tungsten memory management

B. Decrease executor memory and disable caching

C. Set executor memory to default and increase shuffle partitions

D. Disable garbage collection and increase driver memory

Solution

1. Step 1: Understand memory and GC optimization

   Increasing executor memory reduces GC pressure. Tungsten optimizes memory use in Spark.

2. Step 2: Evaluate options for large data processing

   Increase executor memory and enable Tungsten memory management combines more memory with efficient memory management, improving performance.

3. Final Answer:

   Increase executor memory and enable Tungsten memory management -> Option A

4. Quick Check:

   More memory + Tungsten = better performance [OK]

Hint: Combine more memory with Tungsten for best results [OK]

Common Mistakes:

• Decreasing memory worsens GC issues
• Disabling GC causes crashes
• Only increasing shuffle partitions doesn't fix GC