srowen commented on a change in pull request #23919: [MINOR][DOC] Documentation improvement: More detailed explanation of possible "deploy-mode"s URL: https://github.com/apache/spark/pull/23919#discussion_r262524566
########## File path: docs/submitting-applications.md ########## @@ -48,13 +48,22 @@ Some of the commonly used options are: * `application-jar`: Path to a bundled jar including your application and all dependencies. The URL must be globally visible inside of your cluster, for instance, an `hdfs://` path or a `file://` path that is present on all nodes. * `application-arguments`: Arguments passed to the main method of your main class, if any -<b>†</b> A common deployment strategy is to submit your application from a gateway machine -that is -physically co-located with your worker machines (e.g. Master node in a standalone EC2 cluster). -In this setup, `client` mode is appropriate. In `client` mode, the driver is launched directly -within the `spark-submit` process which acts as a *client* to the cluster. The input and -output of the application is attached to the console. Thus, this mode is especially suitable -for applications that involve the REPL (e.g. Spark shell). +<b>†</b>In `client` mode, the driver is launched directly within the `spark-submit` process on +the machine which was used to submit the Spark job, and it will act as a *client* to the cluster. Review comment: OK, maybe best to punt on this. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
