You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "JacobZheng (Jira)" <ji...@apache.org> on 2022/03/29 08:48:00 UTC

[jira] [Updated] (SPARK-38682) Complex calculations with lead to driver oom

     [ https://issues.apache.org/jira/browse/SPARK-38682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

JacobZheng updated SPARK-38682:
-------------------------------
    Description: 
My spark job is working fine in version 3.0.1. After I upgraded to 3.2, the driver would hang during runtime due to oom. The dump file shows that the stageMetrics in SQLAppStatusListener are taking up a lot of memory.I'm wondering if it's related to the SPARK-33016 change, or if the execution plan change has created more stages, causing the driver to run out of memory, or some other reason.
 !screenshot-1.png! 


  was:
My spark job is working fine in version 3.0.1. After I upgraded to 3.2, the driver would hang during runtime due to oom. The dump file shows that the stageMetrics in SQLAppStatusListener are taking up a lot of memory.I'm wondering if it's related to the SPARK-33016 change, or if the execution plan change has created more stages, causing the driver to run out of memory, or some other reason.



> Complex calculations with  lead to driver oom
> ---------------------------------------------
>
>                 Key: SPARK-38682
>                 URL: https://issues.apache.org/jira/browse/SPARK-38682
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 3.2.0
>            Reporter: JacobZheng
>            Priority: Major
>         Attachments: 20220329164645.jpg, screenshot-1.png
>
>
> My spark job is working fine in version 3.0.1. After I upgraded to 3.2, the driver would hang during runtime due to oom. The dump file shows that the stageMetrics in SQLAppStatusListener are taking up a lot of memory.I'm wondering if it's related to the SPARK-33016 change, or if the execution plan change has created more stages, causing the driver to run out of memory, or some other reason.
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org