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

chenk updated SPARK-24015:
--------------------------
      Docs Text:   (was: 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.)
    Description: 
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.

> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to