You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/04/10 01:42:13 UTC
[jira] [Assigned] (SPARK-4848) Allow different Worker
configurations in standalone cluster
[ https://issues.apache.org/jira/browse/SPARK-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apache Spark reassigned SPARK-4848:
-----------------------------------
Assignee: Apache Spark
> Allow different Worker configurations in standalone cluster
> -----------------------------------------------------------
>
> Key: SPARK-4848
> URL: https://issues.apache.org/jira/browse/SPARK-4848
> Project: Spark
> Issue Type: Bug
> Components: Deploy
> Affects Versions: 1.0.0
> Environment: stand-alone spark cluster
> Reporter: Nathan Kronenfeld
> Assignee: Apache Spark
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> On a stand-alone spark cluster, much of the determination of worker specifics, especially one has multiple instances per node, is done only on the master.
> The master loops over instances, and starts a worker per instance on each node.
> This means, if your workers have different values of SPARK_WORKER_INSTANCES or SPARK_WORKER_WEBUI_PORT from each other (or from the master), all values are ignored except the one on the master.
> SPARK_WORKER_PORT looks like it is unread in scripts, but read in code - I'm not sure how it will behave, since all instances will read the same value from the environment.
--
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