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

Posted to issues@spark.apache.org by "Andrew Or (JIRA)" <ji...@apache.org> on 2016/04/06 07:33:25 UTC

[jira] [Resolved] (SPARK-14416) Add thread-safe comments for CoarseGrainedSchedulerBackend's fields

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

Andrew Or resolved SPARK-14416.
-------------------------------
       Resolution: Fixed
         Assignee: Shixiong Zhu
    Fix Version/s: 2.0.0

> Add thread-safe comments for CoarseGrainedSchedulerBackend's fields
> -------------------------------------------------------------------
>
>                 Key: SPARK-14416
>                 URL: https://issues.apache.org/jira/browse/SPARK-14416
>             Project: Spark
>          Issue Type: Improvement
>            Reporter: Shixiong Zhu
>            Assignee: Shixiong Zhu
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> While I was reviewing https://github.com/apache/spark/pull/12078, I found most of CoarseGrainedSchedulerBackend's mutable fields doesn't have any comments about the thread-safe assumptions and it's hard for people to figure out which part of codes should be protected by the lock. 



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