[
https://issues.apache.org/jira/browse/SPARK-22589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabiano Francesconi updated SPARK-22589:
Description:
Mesos offers the capability of [subscribing to multiple
roles|http://mesos.apache.org/documentation/latest/roles/]. I believe that
Spark could easily be extended to opt-in for this specific capability.
>From my understanding, this is the [Spark source
>code|https://github.com/apache/spark/blob/fc45c2c88a838b8f46659ebad2a8f3a9923bc95f/resource-managers/mesos/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerUtils.scala#L94]
> that regulates the subscription to the role. I wonder on whether just passing
>a comma-separated list of frameworks (hence, splitting on that string) would
>already be sufficient to leverage this capability.
Is there any side-effect that this change will cause?
was:
Mesos offers the capability of [subscribing to multiple
roles|http://mesos.apache.org/documentation/latest/roles/]. I believe that
Spark could easily be extended to opt-in for this specific capability.
>From my understanding, this is the [Spark source
>code|https://github.com/apache/spark/blob/fc45c2c88a838b8f46659ebad2a8f3a9923bc95f/resource-managers/mesos/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerUtils.scala#L94]
> that regulates the subscription to the role. I wonder on whether just passing
>a comma-separated list of frameworks (hence, splitting on that string) would
>already be sufficient to leverage this capability.
> Subscribe to multiple roles in Mesos
>
>
> Key: SPARK-22589
> URL: https://issues.apache.org/jira/browse/SPARK-22589
> Project: Spark
> Issue Type: Wish
> Components: Spark Core
>Affects Versions: 2.1.2, 2.2.0
>Reporter: Fabiano Francesconi
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Mesos offers the capability of [subscribing to multiple
> roles|http://mesos.apache.org/documentation/latest/roles/]. I believe that
> Spark could easily be extended to opt-in for this specific capability.
> From my understanding, this is the [Spark source
> code|https://github.com/apache/spark/blob/fc45c2c88a838b8f46659ebad2a8f3a9923bc95f/resource-managers/mesos/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerUtils.scala#L94]
> that regulates the subscription to the role. I wonder on whether just
> passing a comma-separated list of frameworks (hence, splitting on that
> string) would already be sufficient to leverage this capability.
> Is there any side-effect that this change will cause?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
