[jira] [Commented] (SPARK-10102) Fix a race condition that startReceiver may happen before setting trackerState to Started

["Apache Spark (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-10102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702288#comment-14702288 ] 

Apache Spark commented on SPARK-10102:
--------------------------------------

User 'zsxwing' has created a pull request for this issue:
https://github.com/apache/spark/pull/8294

> Fix a race condition that startReceiver may happen before setting trackerState to Started
> -----------------------------------------------------------------------------------------
>
>                 Key: SPARK-10102
>                 URL: https://issues.apache.org/jira/browse/SPARK-10102
>             Project: Spark
>          Issue Type: Bug
>          Components: Streaming
>            Reporter: Shixiong Zhu
>
> Test failure: https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-Maven-with-YARN/HADOOP_PROFILE=hadoop-2.4,label=spark-test/3305/testReport/junit/org.apache.spark.streaming/StreamingContextSuite/stop_gracefully/
> There is a race condition that setting `trackerState` to `Started` could happen after calling `startReceiver`. Then `startReceiver` won't start the receivers because it uses `! isTrackerStarted` to check if ReceiverTracker is stopping or stopped. But actually, `trackerState` is `Initialized` and will be changed to `Started` soon.
> Therefore, we should use `isTrackerStopping || isTrackerStopped`.



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