Skip to content

Commit fdb104a

Browse files
authored
Fix alt-text for resource bottlenecks diagram
Corrected the alt-text in the resource bottlenecks diagram.
1 parent f0c3482 commit fdb104a

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

learn-pr/wwl-databricks/monitor-troubleshoot-optimize-workloads-azure-databricks/includes/4-troubleshoot-repair-spark-jobs-notebooks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ After identifying a problematic job, drill into its longest stage to examine tas
3737

3838
Resource bottlenecks manifest differently depending on which resource is constrained. The compute metrics interface helps you identify these patterns by showing CPU, memory, and network utilization across nodes.
3939

40-
:::image type="content" source="../media/4-identify-resolve-resource-bottlenecks.png" alt-text="Diagram exlaining how to identify and resolve resource bottlenecks." border="false" lightbox="../media/4-identify-resolve-resource-bottlenecks.png":::
40+
:::image type="content" source="../media/4-identify-resolve-resource-bottlenecks.png" alt-text="Diagram explaining how to identify and resolve resource bottlenecks." border="false" lightbox="../media/4-identify-resolve-resource-bottlenecks.png":::
4141

4242
**Memory pressure** appears as high memory utilization across workers or the driver. In the Spark UI, look for spill indicators showing data being written to disk because memory is insufficient. You can address memory issues by increasing worker instance sizes, reducing partition counts, or optimizing transformations to minimize data held in memory.
4343

0 commit comments

Comments
 (0)