diff options
| author | Shixiong Zhu <shixiong@databricks.com> | 2016-01-22 21:20:04 -0800 |
|---|---|---|
| committer | Reynold Xin <rxin@databricks.com> | 2016-01-22 21:20:04 -0800 |
| commit | bc1babd63da4ee56e6d371eb24805a5d714e8295 (patch) | |
| tree | 8aec6a20e3d23574f53d818752df61a28c64d635 /docs/cluster-overview.md | |
| parent | d8fefab4d8149f0638282570c75271ef35c65cff (diff) | |
| download | spark-bc1babd63da4ee56e6d371eb24805a5d714e8295.tar.gz spark-bc1babd63da4ee56e6d371eb24805a5d714e8295.tar.bz2 spark-bc1babd63da4ee56e6d371eb24805a5d714e8295.zip | |
[SPARK-7997][CORE] Remove Akka from Spark Core and Streaming
- Remove Akka dependency from core. Note: the streaming-akka project still uses Akka.
- Remove HttpFileServer
- Remove Akka configs from SparkConf and SSLOptions
- Rename `spark.akka.frameSize` to `spark.rpc.message.maxSize`. I think it's still worth to keep this config because using `DirectTaskResult` or `IndirectTaskResult` depends on it.
- Update comments and docs
Author: Shixiong Zhu <shixiong@databricks.com>
Closes #10854 from zsxwing/remove-akka.
Diffstat (limited to 'docs/cluster-overview.md')
| -rw-r--r-- | docs/cluster-overview.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/cluster-overview.md b/docs/cluster-overview.md index 2810112f52..814e4406cf 100644 --- a/docs/cluster-overview.md +++ b/docs/cluster-overview.md @@ -35,7 +35,7 @@ There are several useful things to note about this architecture: processes, and these communicate with each other, it is relatively easy to run it even on a cluster manager that also supports other applications (e.g. Mesos/YARN). 3. The driver program must listen for and accept incoming connections from its executors throughout - its lifetime (e.g., see [spark.driver.port and spark.fileserver.port in the network config + its lifetime (e.g., see [spark.driver.port in the network config section](configuration.html#networking)). As such, the driver program must be network addressable from the worker nodes. 4. Because the driver schedules tasks on the cluster, it should be run close to the worker |