Memory management and garbage collection in Apache Spark - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the role of memory management in Apache Spark?

Memory management in Apache Spark controls how memory is allocated and used for processing data efficiently, helping to avoid crashes and slowdowns.

beginner

Explain garbage collection in Apache Spark.

Garbage collection automatically frees up memory by removing data objects that are no longer needed during Spark's execution.

intermediate

What are the two main memory regions managed by Spark's Unified Memory Manager?

Spark's Unified Memory Manager divides memory into execution memory (for computations) and storage memory (for caching data).

intermediate

How does Spark handle memory pressure when execution memory is full?

Spark tries to evict cached data from storage memory to free space for execution memory under memory pressure.

advanced

Why is tuning garbage collection important in Spark applications?

Tuning garbage collection reduces pauses and improves performance by efficiently managing how and when memory is cleaned up.

What does Spark's Unified Memory Manager primarily manage?

A Memory for execution and storage

B Disk space

C Network bandwidth

D CPU cores allocation

Spark's Unified Memory Manager manages memory split between execution and storage tasks.

What happens during garbage collection in Spark?

A Unused memory is freed

B Data is saved permanently

C New data is loaded

D CPU usage increases

Garbage collection frees memory by removing objects no longer in use.

If execution memory is full, Spark will try to:

A Allocate more CPU cores

B Stop the job immediately

C Increase disk usage

D Evict cached data from storage memory

Spark evicts cached data to free execution memory when needed.

Why is memory management important in Spark?

A To reduce network traffic

B To increase disk space

C To prevent crashes and improve speed

D To manage user permissions

Proper memory management helps Spark run smoothly and fast.

Which of these is NOT a part of Spark's memory management?

A Execution memory

B User interface design

C Garbage collection

D Storage memory

User interface design is unrelated to Spark's memory management.

Describe how Apache Spark manages memory during data processing.

Think about how Spark splits memory and what it does when memory runs low.

Explain the purpose and effect of garbage collection in Spark applications.

Consider why cleaning memory is important for long-running 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