You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2018/04/19 03:08:00 UTC
[jira] [Commented] (SPARK-24015) Does method
SchedulerBackend.isReady is really well implemented?
[ https://issues.apache.org/jira/browse/SPARK-24015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443509#comment-16443509 ]
Hyukjin Kwon commented on SPARK-24015:
--------------------------------------
[~chenk], is this a question? I think we would have a better answer if you ask this to a mailing list. We don't usually open a JIRA for a question.
I think it's better to ask it to the mailing list first before describing here as a bug.
> Does method SchedulerBackend.isReady is really well implemented?
> ----------------------------------------------------------------
>
> Key: SPARK-24015
> URL: https://issues.apache.org/jira/browse/SPARK-24015
> Project: Spark
> Issue Type: Bug
> Components: Scheduler
> Affects Versions: 2.3.0
> Reporter: chenk
> Priority: Minor
>
> The mothod *isReady* in the interface *SchedulerBackend*,which implement by *CoarseGrainedSchedulerBackend* , as well as has default value is True.
> And, the implemention in *CoarseGrainedSchedulerBackend* use *sufficientResourcesRegistered* mothed to check it , which default value is True too.
> So,What does the meaning of the *isReady* method? Because it will alway return true actually.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org