You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 05:37:43 UTC

[jira] [Resolved] (SPARK-2545) Add a diagnosis mode for closures to figure out what they're bringing in

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

Hyukjin Kwon resolved SPARK-2545.
---------------------------------
    Resolution: Incomplete

> Add a diagnosis mode for closures to figure out what they're bringing in
> ------------------------------------------------------------------------
>
>                 Key: SPARK-2545
>                 URL: https://issues.apache.org/jira/browse/SPARK-2545
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>            Reporter: Aaron Davidson
>            Priority: Major
>              Labels: bulk-closed
>
> Today, it's pretty hard to figure out why your closure is bigger than expected, because it's not obvious what objects are being included or who is including them. We should have some sort of diagnosis available to users with very large closures that displays the contents of the closure.



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

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