[ 
https://issues.apache.org/jira/browse/SPARK-16455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406375#comment-15406375
 ] 

Kay Ousterhout commented on SPARK-16455:
----------------------------------------

Given that this feature is only needed for an internal feature that's not part 
of the main Spark code, I don't think it makes sense to add additional 
complexity to Spark to support it.

Also, isClusterAvailableForNewOffers is in a class that's private to Spark, so 
it doesn't make sense to add this Spark-private method that's not used anywhere 
in Spark.

I'd be in favor of closing this as "will not fix", unless others have reasons 
they think this makes sense to add?

> Add a new hook in CoarseGrainedSchedulerBackend in order to stop scheduling 
> new tasks when cluster is restarting
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-16455
>                 URL: https://issues.apache.org/jira/browse/SPARK-16455
>             Project: Spark
>          Issue Type: New Feature
>          Components: Scheduler
>            Reporter: YangyangLiu
>            Priority: Minor
>
> In our case, we are implementing a new mechanism which will let driver 
> survive when cluster is temporarily down and restarting. So when the service 
> provided by cluster is not available, scheduler should stop scheduling new 
> tasks. I added a hook inside CoarseGrainedSchedulerBackend class, in order to 
> avoid new task scheduling when it's necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to