[jira] [Updated] (SPARK-4949) shutdownCallback in SparkDeploySchedulerBackend should be enclosed by synchronized block.
[ https://issues.apache.org/jira/browse/SPARK-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-4949: - Priority: Minor (was: Major) Target Version/s: (was: 1.3.0) Affects Version/s: (was: 1.3.0) 1.2.1 Assignee: Kousuke Saruta > shutdownCallback in SparkDeploySchedulerBackend should be enclosed by > synchronized block. > - > > Key: SPARK-4949 > URL: https://issues.apache.org/jira/browse/SPARK-4949 > Project: Spark > Issue Type: Bug > Components: Scheduler >Affects Versions: 1.2.1 >Reporter: Kousuke Saruta >Assignee: Kousuke Saruta >Priority: Minor > > A variable `shutdownCallback` in SparkDeploySchedulerBackend can be accessed > from multiple threads so it should be enclosed by synchronized block. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-4949) shutdownCallback in SparkDeploySchedulerBackend should be enclosed by synchronized block.
[ https://issues.apache.org/jira/browse/SPARK-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-4949: - Component/s: (was: Spark Core) Scheduler > shutdownCallback in SparkDeploySchedulerBackend should be enclosed by > synchronized block. > - > > Key: SPARK-4949 > URL: https://issues.apache.org/jira/browse/SPARK-4949 > Project: Spark > Issue Type: Bug > Components: Scheduler >Affects Versions: 1.3.0 >Reporter: Kousuke Saruta > > A variable `shutdownCallback` in SparkDeploySchedulerBackend can be accessed > from multiple threads so it should be enclosed by synchronized block. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
