Spark UI for debugging performance in Apache Spark - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a Spark session with the UI enabled.

Apache Spark

from pyspark.sql import SparkSession
spark = SparkSession.builder.appName('TestApp').[1]()

Drag options to blanks, or click blank then click option'

AlaunchUI

BenableUI

CgetOrCreate

DstartUI

Attempts:

3 left

💡 Hint

Common Mistakes

Using a method that does not exist like enableUI or startUI.

Forgetting to call a method to create the session.

The method getOrCreate() starts the Spark session and enables the UI by default.

2fill in blank

medium

Complete the code to access the Spark UI web URL from the SparkContext.

Apache Spark

ui_url = spark.sparkContext.[1]

Drag options to blanks, or click blank then click option'

AuiWebUrl()

BuiWebUrl

CgetUIUrl()

DgetUIWebUrl

Attempts:

3 left

💡 Hint

Common Mistakes

Calling uiWebUrl as a method with parentheses.

Using incorrect method names like getUIUrl.

The uiWebUrl property gives the Spark UI web address as a string.

3fill in blank

hard

Fix the error in the code to get the duration of the last Spark job from the Spark UI listener.

Apache Spark

listener = spark.sparkContext.statusTracker
last_job = listener.getJobIdsForGroup([1])[-1]
duration = listener.getJobInfo(last_job).[2]

Drag options to blanks, or click blank then click option'

A0, 'completionTime'

B0, 'duration'

CNone, 'completionTime'

DNone, 'duration'

Attempts:

3 left

💡 Hint

Common Mistakes

Using None instead of 0 for the job group.

Using 'duration' which is not a valid property.

The first argument is 0 to get the first job group, and 'completionTime' is the correct attribute for duration.

4fill in blank

hard

Fill both blanks to create a dictionary of stage IDs and their durations from the Spark UI listener.

Apache Spark

stage_info = {stage.stageId: stage.[1] for stage in spark.sparkContext.statusTracker.[2]()}

Drag options to blanks, or click blank then click option'

AcompletionTime

BgetActiveStages

CgetAllStages

Dduration

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'duration' instead of 'completionTime'.

Using 'getActiveStages' which returns only active stages.

Use 'completionTime' for stage duration and 'getAllStages' to get all stages.

5fill in blank

hard

Fill all three blanks to filter stages with duration greater than 1000 ms and create a dictionary of their IDs and durations.

Apache Spark

filtered_stages = {stage.[1]: stage.[2] for stage in spark.sparkContext.statusTracker.[3]() if stage.completionTime and stage.completionTime > 1000}

Drag options to blanks, or click blank then click option'

AstageId

BcompletionTime

CgetAllStages

DgetActiveStages

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'getActiveStages' which misses completed stages.

Using wrong property names like 'duration'.

Use 'stageId' and 'completionTime' properties and 'getAllStages()' method to filter stages by duration.

Practice

1. What is the primary purpose of the Spark UI when running Spark jobs?

easy

A. To monitor and debug the performance of Spark jobs

B. To write Spark code interactively

C. To store Spark job results permanently

D. To schedule Spark jobs on a cluster

Solution

1. Step 1: Understand Spark UI role

   The Spark UI is designed to help users see how their Spark jobs are running and where delays or resource issues occur.

2. Step 2: Differentiate from other tools

   It is not for writing code, storing results, or scheduling jobs but for monitoring and debugging performance.

3. Final Answer:

   To monitor and debug the performance of Spark jobs -> Option A

4. Quick Check:

   Spark UI = Performance monitoring [OK]

Hint: Spark UI shows job speed and resource use [OK]

Common Mistakes:

• Thinking Spark UI is for coding
• Confusing Spark UI with data storage
• Assuming Spark UI schedules jobs

2. Which URL do you typically use to access the Spark UI on the driver node?

easy

A. http://localhost:8080

B. http://localhost:5000

C. http://localhost:4040

D. http://localhost:7077

Solution

1. Step 1: Recall default Spark UI port

   The Spark UI runs on port 4040 by default on the driver node.

2. Step 2: Verify other ports

   Ports 8080, 5000, and 7077 are used for other services, not Spark UI.

3. Final Answer:

   http://localhost:4040 -> Option C

4. Quick Check:

   Default Spark UI port = 4040 [OK]

Hint: Spark UI default port is 4040 [OK]

Common Mistakes:

• Using common web ports like 8080 or 5000
• Confusing Spark master port 7077 with UI port
• Not including the correct port in URL

3. Given the Spark UI's 'Stages' tab shows a stage with a high 'Task Time' and many 'Shuffle Read' bytes, what does this indicate?

medium

A. The stage is CPU-bound with little data movement

B. The stage is slow due to heavy data shuffling between nodes

C. The stage has no tasks running

D. The stage is waiting for user input

Solution

1. Step 1: Interpret 'Task Time' and 'Shuffle Read'

   High 'Task Time' means tasks take long to complete; many 'Shuffle Read' bytes mean lots of data moves between nodes.

2. Step 2: Understand impact on performance

   Heavy shuffling often slows stages because data transfer over network is costly.

3. Final Answer:

   The stage is slow due to heavy data shuffling between nodes -> Option B

4. Quick Check:

   High shuffle + task time = slow stage due to data movement [OK]

Hint: High shuffle read means slow data transfer stage [OK]

Common Mistakes:

• Assuming high task time means CPU only
• Ignoring shuffle data impact
• Thinking no tasks are running

4. You notice in the Spark UI 'Executors' tab that one executor has very high CPU usage but low task completion rate. What is the likely issue?

medium

A. Executor is overloaded or stuck on a task

B. Executor is idle and not processing tasks

C. Executor has finished all tasks successfully

D. Executor is waiting for input data

Solution

1. Step 1: Analyze CPU usage vs task completion

   High CPU usage with low task completion suggests the executor is busy but not finishing tasks, possibly stuck or overloaded.

2. Step 2: Rule out other options

   Idle executors have low CPU; finished executors don't show high CPU; waiting executors usually show low CPU.

3. Final Answer:

   Executor is overloaded or stuck on a task -> Option A

4. Quick Check:

   High CPU + low completion = stuck executor [OK]

Hint: High CPU but few tasks done means stuck executor [OK]

Common Mistakes:

• Confusing idle with high CPU
• Assuming high CPU means finished tasks
• Ignoring stuck task possibility

5. You want to improve a Spark job's performance by reducing shuffle overhead. Which Spark UI tab and metric should you focus on to identify the main shuffle bottleneck?

hard

A. SQL tab; review query text

B. Jobs tab; check job submission time

C. Executors tab; monitor memory usage only

D. Stages tab; look for high Shuffle Read and Shuffle Write bytes

Solution

1. Step 1: Identify shuffle bottleneck metrics

   The 'Stages' tab shows detailed metrics including Shuffle Read and Shuffle Write bytes, which indicate shuffle data volume.

2. Step 2: Understand why other tabs are less relevant

   Jobs tab shows overall job info but not shuffle details; Executors tab shows resource use but not shuffle specifics; SQL tab shows query but not shuffle metrics.

3. Final Answer:

   Stages tab; look for high Shuffle Read and Shuffle Write bytes -> Option D

4. Quick Check:

   Shuffle bottleneck = Stages tab shuffle bytes [OK]

Hint: Check Stages tab for shuffle bytes to find bottlenecks [OK]

Common Mistakes:

• Looking only at job submission time
• Ignoring shuffle metrics in Stages tab
• Focusing on memory without shuffle data