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

Posted to issues@spark.apache.org by "Shixiong Zhu (JIRA)" <ji...@apache.org> on 2016/11/08 21:19:59 UTC

[jira] [Resolved] (SPARK-18280) Potential deadlock in `StandaloneSchedulerBackend.dead`

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

Shixiong Zhu resolved SPARK-18280.
----------------------------------
       Resolution: Fixed
         Assignee: Shixiong Zhu
    Fix Version/s: 2.1.0
                   2.0.3

> Potential deadlock in `StandaloneSchedulerBackend.dead`
> -------------------------------------------------------
>
>                 Key: SPARK-18280
>                 URL: https://issues.apache.org/jira/browse/SPARK-18280
>             Project: Spark
>          Issue Type: Bug
>    Affects Versions: 1.6.2, 2.0.0, 2.0.1
>            Reporter: Shixiong Zhu
>            Assignee: Shixiong Zhu
>             Fix For: 2.0.3, 2.1.0
>
>
> "StandaloneSchedulerBackend.dead" is called in a RPC thread, so it should not call "SparkContext.stop" in the same thread. "SparkContext.stop" will block until all RPC threads exit, if it's called inside a RPC thread, it will be dead-lock.



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