[jira] [Created] (SPARK-14676) Catch, wrap, and re-throw exceptions from Await.result in order to capture full stacktrace

["Josh Rosen (JIRA)" <ji...@apache.org>]

Josh Rosen created SPARK-14676:
----------------------------------

             Summary: 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


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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org