You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Kousuke Saruta (JIRA)" <ji...@apache.org> on 2014/09/29 08:39:33 UTC
[jira] [Closed] (SPARK-3567) appId field in
SparkDeploySchedulerBackend should be volatile
[ https://issues.apache.org/jira/browse/SPARK-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kousuke Saruta closed SPARK-3567.
---------------------------------
Resolution: Fixed
> appId field in SparkDeploySchedulerBackend should be volatile
> -------------------------------------------------------------
>
> Key: SPARK-3567
> URL: https://issues.apache.org/jira/browse/SPARK-3567
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.2.0
> Reporter: Kousuke Saruta
> Assignee: Kousuke Saruta
> Fix For: 1.2.0
>
>
> appId field in SparkDeploySchedulerBackend is set by AppClient.ClientActor#receiveWithLogging and appId is referred via SparkDeploySchedulerBackend#applicationId.
> A thread which runs AppClient.ClientActor and a thread invoking SparkDeploySchedulerBackend#applicationId can be another threads so appId should be volatile.
--
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