You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Jongyoul Lee (JIRA)" <ji...@apache.org> on 2015/01/12 02:29:34 UTC
[jira] [Updated] (SPARK-5197) Support external shuffle service in
fine-grained mode on mesos cluster
[ https://issues.apache.org/jira/browse/SPARK-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jongyoul Lee updated SPARK-5197:
--------------------------------
Description:
I think dynamic allocation is almost satisfied on mesos' fine-grained mode, which already offers resources dynamically, and returns automatically when a task is finished. It, however, doesn't have a mechanism on support external shuffle service like yarn's way, which is AuxiliaryService. Because mesos doesn't support AusiliaryService, we think a different way to do this.
- Launching a shuffle service like a spark job on same cluster
-- Pros
--- Support multi-tenant environment
--- Almost same way like yarn
-- Cons
--- Control long running 'background' job - service - when mesos runs
--- Satisfy all slave - or host - to have one shuffle service all the time
- Launching jobs within shuffle service
-- Pros
--- Easy to implement
--- Don't consider whether shuffle service exists or not.
-- Cons
--- exists multiple shuffle services under multi-tenant environment
--- Control shuffle service port dynamically on multi-user environment
In my opinion, the first one is better idea to support external shuffle service. Please leave comments.
was:
I think dynamic allocation is almost satisfied on mesos' fine-grained mode, which already offers resources dynamically, and returns automatically when a task is finished. We, however, don't have a mechanism on support external shuffle service like yarn's way, which is AuxiliaryService. Because mesos doesn't support AusiliaryService, we think a different way to do this.
- Launching a shuffle service like a spark job on same cluster
-- Pros
--- Support multi-tenant environment
--- Almost same way like yarn
-- Cons
--- Control long running 'background' job - service - when mesos runs
--- Satisfy all slave - or host - to have one shuffle service all the time
- Launching jobs within shuffle service
-- Pros
--- Easy to implement
--- Don't consider whether shuffle service exists or not.
-- Cons
--- exists multiple shuffle services under multi-tenant environment
--- Control shuffle service port dynamically on multi-user environment
In my opinion, the first one is better idea to support external shuffle service. Please leave comments.
> Support external shuffle service in fine-grained mode on mesos cluster
> ----------------------------------------------------------------------
>
> Key: SPARK-5197
> URL: https://issues.apache.org/jira/browse/SPARK-5197
> Project: Spark
> Issue Type: Improvement
> Components: Deploy, Mesos, Shuffle
> Reporter: Jongyoul Lee
>
> I think dynamic allocation is almost satisfied on mesos' fine-grained mode, which already offers resources dynamically, and returns automatically when a task is finished. It, however, doesn't have a mechanism on support external shuffle service like yarn's way, which is AuxiliaryService. Because mesos doesn't support AusiliaryService, we think a different way to do this.
> - Launching a shuffle service like a spark job on same cluster
> -- Pros
> --- Support multi-tenant environment
> --- Almost same way like yarn
> -- Cons
> --- Control long running 'background' job - service - when mesos runs
> --- Satisfy all slave - or host - to have one shuffle service all the time
> - Launching jobs within shuffle service
> -- Pros
> --- Easy to implement
> --- Don't consider whether shuffle service exists or not.
> -- Cons
> --- exists multiple shuffle services under multi-tenant environment
> --- Control shuffle service port dynamically on multi-user environment
> In my opinion, the first one is better idea to support external shuffle service. Please leave comments.
--
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