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/08/19 05:16:45 UTC
[jira] [Updated] (SPARK-10102) Fix a race condition that
startReceiver may happen before setting trackerState to Started
[ https://issues.apache.org/jira/browse/SPARK-10102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tathagata Das updated SPARK-10102:
----------------------------------
Assignee: Shixiong Zhu
> 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
> Assignee: Shixiong Zhu
> Fix For: 1.5.0
>
>
> 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