You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Holden Karau (Jira)" <ji...@apache.org> on 2020/06/26 20:21:00 UTC
[jira] [Commented] (SPARK-32111) Cleanup locks and docs in
CoarseGrainedSchedulerBackend
[ https://issues.apache.org/jira/browse/SPARK-32111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146613#comment-17146613 ]
Holden Karau commented on SPARK-32111:
--------------------------------------
I'm working on this since I'm in the code anyways for decommissioning.
> Cleanup locks and docs in CoarseGrainedSchedulerBackend
> -------------------------------------------------------
>
> Key: SPARK-32111
> URL: https://issues.apache.org/jira/browse/SPARK-32111
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 3.1.0
> Reporter: Holden Karau
> Priority: Trivial
>
> Our locking is inconsistent inside of CoarseGrainedSchedulerBackend. In production this doesn't matter because the methods in are called from inside of ThreadSafeRPC but it would be better to cleanup the locks and docs to be consistent especially since other schedulers inherit from CoarseGrainedSchedulerBackend.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org