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

Posted to issues@spark.apache.org by "Tathagata Das (JIRA)" <ji...@apache.org> on 2015/07/17 23:01:04 UTC

[jira] [Updated] (SPARK-5681) Calling graceful stop() immediately after start() on StreamingContext should not get stuck indefinitely

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

Tathagata Das updated SPARK-5681:
---------------------------------
    Assignee: Shixiong Zhu

> Calling graceful stop() immediately after start() on StreamingContext should not get stuck indefinitely
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-5681
>                 URL: https://issues.apache.org/jira/browse/SPARK-5681
>             Project: Spark
>          Issue Type: Bug
>          Components: Streaming
>            Reporter: Liang-Chi Hsieh
>            Assignee: Shixiong Zhu
>             Fix For: 1.5.0
>
>
> Sometimes the receiver will be registered into tracker after ssc.stop is called. Especially when stop() is called immediately after start(). So the receiver doesn't get the StopReceiver message from the tracker. In this case, when you call stop() in graceful mode, stop() would get stuck indefinitely.



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