[ 
https://issues.apache.org/jira/browse/SPARK-25380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611012#comment-16611012
 ] 

Marcelo Vanzin commented on SPARK-25380:
----------------------------------------

Another bit of information that would be useful is the breakdown of memory 
usage of the {{SQLExecutionUIData}} instances. They seem to hold a lot more 
memory than just the plan graph structures do, it would be nice to know what 
exactly is holding on to that memory.

(Assuming you can't share the heap dump...)

> Generated plans occupy over 50% of Spark driver memory
> ------------------------------------------------------
>
>                 Key: SPARK-25380
>                 URL: https://issues.apache.org/jira/browse/SPARK-25380
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 2.3.1
>         Environment: Spark 2.3.1 (AWS emr-5.16.0)
>  
>            Reporter: Michael Spector
>            Priority: Minor
>         Attachments: Screen Shot 2018-09-06 at 23.19.56.png, heapdump_OOM.png
>
>
> When debugging an OOM exception during long run of a Spark application (many 
> iterations of the same code) I've found that generated plans occupy most of 
> the driver memory. I'm not sure whether this is a memory leak or not, but it 
> would be helpful if old plans could be purged from memory anyways.
> Attached are screenshots of OOM heap dump opened in JVisualVM.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to