You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2016/04/27 20:00:16 UTC
[jira] [Resolved] (SPARK-14729) Implement an existing cluster
manager with New ExternalClusterManager interface
[ https://issues.apache.org/jira/browse/SPARK-14729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcelo Vanzin resolved SPARK-14729.
------------------------------------
Resolution: Fixed
Assignee: Hemant Bhanawat
Fix Version/s: 2.0.0
> Implement an existing cluster manager with New ExternalClusterManager interface
> -------------------------------------------------------------------------------
>
> Key: SPARK-14729
> URL: https://issues.apache.org/jira/browse/SPARK-14729
> Project: Spark
> Issue Type: Improvement
> Components: Scheduler
> Reporter: Hemant Bhanawat
> Assignee: Hemant Bhanawat
> Priority: Minor
> Fix For: 2.0.0
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> SPARK-13904 adds an ExternalClusterManager interface to Spark to allow external cluster managers to spawn Spark components.
> This JIRA tracks following suggestion from [~rxin]:
> 'One thing - can you guys try to see if you can implement one of the existing cluster managers with this, and then we can make sure this is a proper API? Otherwise it is really easy to get removed because it is currently unused by anything in Spark.'
--
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