[
https://issues.apache.org/jira/browse/SPARK-14676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248257#comment-15248257
]
Reynold Xin commented on SPARK-14676:
-------------------------------------
[~joshrosen] I didn't merge this in 1.6.2 because it is a bit too big to
backport. Let me know if you want to create a smaller patch for 1.6.
> Catch, wrap, and re-throw exceptions from Await.result in order to capture
> full stacktrace
> ------------------------------------------------------------------------------------------
>
> Key: SPARK-14676
> URL: https://issues.apache.org/jira/browse/SPARK-14676
> Project: Spark
> Issue Type: Bug
> Reporter: Josh Rosen
> Assignee: Josh Rosen
> Fix For: 2.0.0
>
>
> When {{Await.result}} throws an exception which originated from a different
> thread, the resulting stacktrace doesn't include the path leading to the
> {{Await.result()}} call itself, making it difficult to identify the impact of
> these exceptions. For example, I've seen cases where broadcast cleaning
> errors propagate to the main thread and crash it but the resulting stacktrace
> doesn't include any of the main thread's code, making it difficult to
> pinpoint which exception crashed that thread.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
