Github user jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/8629#discussion_r39024388
--- Diff: docs/cluster-overview.md ---
@@ -33,9 +34,9 @@ There are several useful things to note about this
architecture:
2. Spark is agnostic to the underlying cluster manager. As long as it can
acquire executor
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
- section](configuration.html#networking)). As such, the driver program
must be network
+3. The driver program must listen for and accept incoming connections from
its executors throughout
--- End diff --
The additional spaces at the end. Thanks a lot for reviewing the change and
accepting it!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
